Builder's guide · Section 11
Map your business to GAAPcore
GAAPcore covers 121 transaction types. Map each activity from your worksheet (section 4) to the area that handles it, and build only the areas you need.
| Area | Routes | What your console uses it for |
|---|---|---|
| Foundations | /v1/companies, /v1/ledger/fiscal-*, /v1/number-series | Companies, fiscal years and periods, document numbering |
| General ledger | /v1/ledger/accounts, control-accounts, manual-journals, journal-entries, trial-balance | Chart of accounts, control account mapping, manual journals (draft, post, reverse), account inquiry |
| Banking | /v1/banking/… | Bank accounts, money in and out, transfers, statement import, matching, reconciliation |
| Master data | /v1/sales/customers, /v1/purchasing/vendors, /v1/inventory/products, units, warehouses, /v1/tax/… | Customers, vendors, products, units of measure, warehouses and bins, sales tax jurisdictions and rates |
| Purchasing and payables | /v1/purchasing/… | Purchase orders, goods receipts (FIFO layers), vendor bills with holds and approval, payments, credits, returns, AP aging |
| Inventory | /v1/inventory/… | Put-away, bin and warehouse transfers, adjustments, cycle counts, available to promise, valuation |
| Production | /v1/production/… | Bills of material (recipes), production orders, component issues, finished goods, labor and overhead, variances |
| Sales and receivables | /v1/sales/…, /v1/ar/… | Sales orders, credit holds, picks and shipments, invoices with sales tax, receipts, credit memos, returns, dunning, write-offs, AR aging, statements |
| Fixed assets and leases | /v1/assets/…, /v1/leases/… | Asset register, depreciation runs, disposals, impairments; lessee leases, schedules, modifications |
| Reporting | /v1/ledger/income-statement, balance-sheet, cash-flow-statement, financial-statements, subledgers | Statements, notes, the issued statement set, subledger tie-outs |
| Groups | /v1/group/… | Company groups, intercompany sales and transfers, consolidated statements |
The full list of routes and fields is api/openapi.yaml. Each transaction type also has a written specification under catalog/ (business trigger, journal entries, validations, reversal, US GAAP notes), which is the best place to learn what a document does before building its screen.
Modelling tips from the reference build
- Bank cash moves only through bank documents. Once a GL account is a bank's cash account, manual journals to it are refused. Show a bank's register as its GL activity, marking what is still outstanding.
- Give each bank document the bank's reference (
bank_reference). Then auto-matching pairs statement lines with book items. For a fee or interest with no book item yet, create the document from the statement line and match again. - Receive at the order's cost. The receiving screen takes quantities, not prices. A different price on the vendor's bill is the bill's to settle.
- Put process losses in the recipe. Roasting, baking or trimming needs no “shrink” field: the bill of material lists more input than output, so the output's cost carries the loss.
- What the books don't need, the console keeps: price lists, photos, preferences. Don't stretch the ledger to hold them.