Skip to main content
Core Financials is the double-entry engine underneath everything else in DualEntry. It holds the chart of accounts every transaction posts against, the payable and receivable subledgers your team works in daily, the schedules that post depreciation and amortization on their own, and the close tooling that turns a month of activity into locked, reportable books.

​
What this section covers

Core Financials breaks into the ledger itself, the subledgers that feed it, and the close process that seals a period.
  • General Ledger: the chart of accounts and the journal entries posted against it, including recurring entries, accruals, statistical accounts, and allocation journals. Every other module in DualEntry ultimately resolves to a debit and a credit here.
  • Accounts Payable: the vendor spend lifecycle, from bill entry and approval routing through vendor payments, purchase orders, billable expenses, and 1099 tracking.
  • Accounts Receivable: the revenue side, covering invoicing, automated dunning, customer payments, customer statements, and sales order management.
  • Fixed asset management: assets from acquisition through depreciation schedules, multi-book depreciation, disposals, and revaluations.
  • Prepaid expense amortization: amortization schedules that post their monthly entries automatically and track the remaining balance through termination.
  • Bank Connections: linking bank accounts for automated transaction feeds, mapping them to GL accounts, and reconnecting a stale feed.
  • Close Management: the close checklist and the workflows it points to, including Bank Match, reconciliation, currency revaluation, and period locking.
Tax management sits in this part of the URL tree but is documented under Platform Configuration, since configuring tax codes and jurisdictions is a setup task rather than a daily one. See Tax Management for US sales and use tax, VAT, and GST.

​
How the modules fit together

The subledgers feed the ledger, and the ledger feeds the close. Understanding that direction of travel explains where to fix a number when it looks wrong. AP, AR, fixed assets, and prepaid amortization are all subledgers: they capture detail in their own workspace and post summarized debits and credits to the general ledger in real time. There is no nightly sync to wait for, so a bill approved this morning is already in the trial balance. When a GL balance looks wrong, the correction usually belongs in the subledger that produced it rather than in a manual journal entry against the account. Bank Connections sit slightly apart. They bring in third-party transaction data rather than generating accounting entries, and that data is what Bank Match pairs against entries the subledgers already posted. Close Management then consumes all of it: reconciliations confirm each balance-sheet account against its supporting detail, revaluation restates open foreign-currency balances, and period locking blocks further posting once the period is final. Everything downstream reads from the same ledger. Reporting and Analytics builds statements from it, and Revenue Recognition maintains its own subledger that posts here like any other.

​
Where to start

Your starting point depends on whether you are standing the ledger up or running it. If you are setting up a new organization, begin with the General Ledger to define your chart of accounts, then connect your banks in Bank Connections so transaction history is flowing before your first close. The Get Started section covers the wider implementation sequence, including migrating balances from a prior system. If the ledger is already live and you are running a period, work from the Month-End Close Checklist, which sequences the reconciliations and reviews that have to happen before you can lock the period.
Last modified on September 14, 2026