GL Code Account

GL Code Account maps SquareOS invoices, taxes, payments, refunds, discounts, and exports into accounting accounts and journal batches for finance reconciliation.

What this page is for

GL Code Account maps SquareOS invoices, taxes, payments, refunds, discounts, and exports into accounting accounts and journal batches for finance reconciliation.

Who should use it

Owner, finance, accountant, platform admin

Where to find it

/admin/gl-code-account

Before you start

GL account fields are Code, Name, Account type, Description, and Active.
GL mapping rule fields are Rule name, GL account, Source type, Debit / Credit, Item type, Payment mode, Tax code, Priority, Criteria JSON, and Active.
Journal engine fields are Period start, Period end, and Export format, with Create export batch and Generate journals actions.
Account type should match the accounting chart: Asset, Liability, Revenue, Expense, or Equity.
Source type decides what event the rule catches: invoice item, tax, payment, refund, or discount.
Debit / Credit must be approved by finance because the wrong side creates wrong journals.
Priority decides which mapping wins when multiple rules could match. Criteria JSON should be valid JSON and narrow enough to avoid accidental postings.
Open unmapped count should be reviewed before treating journals or export batches as finance-ready.

Daily workflow

Seed defaults if the owner accepts the starter chart, then edit codes and names to match the accountant chart.
Create mapping rules for plan revenue, add-on revenue, joining fee, GST, cash/UPI/bank collections, refunds, and discounts.
Generate journals for a test period, compare debit/credit totals, then create export batch in the required format.

Watch out

Do not generate final journal exports until unmapped events are reviewed and finance agrees with debit/credit behavior.

Use the left menu to open related pages in Admin Settings.
Use Ask Docs for questions that are already covered in this public documentation.