Domain
How accounting actually works. The layer that makes this accounting software.
- Documents
- 13
- Terms defined
- 287
- The accounting modelEvery component in Lopifi sits on top of one data model. If the model is wrong, no amount of design saves the product. This document is the model.
- Periods & the closeThe month-end close in accounting software: fiscal calendars, period states, cutoff, reconciliation vs tie-out, adjusting entries and restatement.
- Statement semanticsWhat each statement means, how it's structured, and what the components must therefore enforce.
- Schedules, accruals & roll-forwardsThe supporting evidence layer. Every balance sheet account needs a schedule behind it, and the schedule must tie.
- Order to cash (AR)The complete receivables stack: quote → order → fulfilment → invoice → collection → cash application → revenue.
- Procure to pay (AP)The complete payables stack: requisition → PO → receipt → bill → approval → payment → reconciliation. AP is where fraud happens and where controls matter most. The design consequence: Every AP screen is a control surface. Approval, segregation of duties, and duplicate detection are not features bolt
- Cash & treasuryCash is the only balance sheet account with an independent third party asserting what it should be. That makes it both the most verifiable account and the one where a break matters most.
- Controls & auditAccounting software is not a database with forms on top. It is a system of controls, and the UI is where most of those controls are actually enforced.
- Multi-entity & FXConsolidation and currency are where finance UIs quietly produce wrong numbers, because both involve summing things that look summable and aren't.
- Metric definitionsEvery metric in this system ships with its formula, its period, its inputs, and its source. A KPI without a definition is a number people argue about in meetings.
- LexiconOne word per concept, used identically in code, UI copy, and documentation. Terminology drift is the fastest way to make a financial product feel amateur to the people who use it professionally.
- Lopifi APIs: Xero, QuickBooks Online, NetSuiteThree general ledgers, three different opinions about what an invoice is. This document compares them object by object, so a component built on one does not quietly break on another.
- US GAAP, and where these rules come fromThis system states a lot of accounting rules. Revenue is earned on delivery. Depreciation allocates cost rather than measuring value. A statement of cash flows has three sections and reconciles to the change in cash. A posted entry is reversed, never edited.
What each document covers
Lopifi APIs: Xero, QuickBooks Online, NetSuite
- 1. The three APIs at a glance
- 2. Identity, tenancy, and the entity boundary
- 3. Chart of accounts
- 4. Parties: contacts, customers, vendors
- 5. Sales invoices (AR)
- 6. Bills (AP)
- 7. Payments and allocation
- 8. Credit notes, refunds, and the negative document
- 9. Journals and the general ledger
- 10. Items, products, and services
- 11. Tax
- 12. Dimensions: tracking, class, department, segment
- 13. Periods, locking, and the close
- 14. Attachments, memos, and the audit trail
- 15. Reports
- 16. Mechanics: reading, writing, limits
- 17. The canonical model
- 18. What this changes in the UI
- 19. Naming crosswalk
- 20. Using this document
From here
The same material, reached the other way round — by the word, by the component, or by the thing running.
- FoundationsGrid, shape, colour, elevation, type, numerics.Doc
- CatalogAll 179 components, specified before they are written.Doc
- 287 terms defined in this sectionEach one a page, generated from the document that defines it.Term
- The components, runningEvery implemented component on one set of pages, with real figures in it.Live