Accounting rules
Configuring which account each sale, VAT amount, payment, rounding, paid-in/paid-out and gift card is posted to, the order rules are matched in, the minimum set a store needs, and when a change takes effect.
Configuring which account each sale, VAT amount, payment, rounding, paid-in/paid-out and gift card is posted to, the order rules are matched in, the minimum set a store needs, and when a change takes effect.
Looking at a store's accounts for a business day, drilling into the transactions behind an account, downloading them as a spreadsheet, and recomputing or re-exporting, through the General Ledger API or the General Ledger tool.
What to do when journals were exported with a wrong accounting rule: fix the rule, recompute the days, and receive a correction journal holding only the difference. Also: resending journals with re-export, limits, and blocked days.
General Ledger turns every sale, return and payment in your stores into accounting entries, adds them up per store and business day, and sends the result to your accounting system.
The JSON schema of a General Ledger journal event (gle.public.event.general-ledger.v1).
When General Ledger sends a store's day, what a journal contains, and why a later journal for the same day holds only the difference.
How General Ledger turns a sale, a return, a payment, rounding, paid-in/paid-out and gift cards into debits and credits, and why a return is a debit rather than a negative amount.
Subscribing to General Ledger journals through External Events or Pub/Sub, and the rules an accounting integration must follow: post every journal, skip duplicates by journal ID, and never replace a day with its latest journal.