Automatic journal entries in Skyline Nexus ERP

What automatic journal entries are

Automatic journal entries are ledger postings that a system generates from a business document, such as an invoice, a supplier bill or a payroll run, using predefined rules about which accounts to debit and credit. They matter because they remove re-keying, post at the moment the transaction happens and apply the same accounting every time, which makes errors systematic and therefore findable.

The trade-off is that a wrong rule is wrong for every document. A manual bookkeeper who misposts one invoice makes one error; a misconfigured mapping misposts every invoice in its category until someone notices. That is why this guide spends as much time on configuration and checking as on the postings themselves. It explains the general mechanism first, then the exact switches, mappings and checks in Skyline Nexus ERP.

From source document to ledger: the posting rule

Every automatic posting answers three questions. Which event triggers it: saving a final invoice, receiving goods, recording a payment? Which accounts does it hit, a step often called account determination? And which dimensions travel with the lines: branch, cost centre, project, customer or supplier? A good design keeps the rules in configuration, not in code, so the finance team can see and change them.

Posting can be immediate or batched. Batch posting, a daily or month-end run that summarises documents into one journal, was common when computing was expensive, but it leaves the ledger stale and makes drilling from a ledger line to a document harder. Skyline Nexus ERP posts each document individually as a background job straight after it is saved, so the ledger is current within moments and every journal traces to one source document. Our guide on how ERP modules actually integrate discusses the design choice more broadly.

Switching automatic posting on

In Skyline Nexus ERP the switches live under Fiscal Authority, Settings, General Settings, Auto-Post Settings, described on screen as Automatically create and post journal entries from transactions. There is one toggle per document family. All of them default to off, so an administrator must switch on the ones the business uses. That default is deliberate: it lets you complete the chart of accounts, mappings and fiscal periods before the first document posts, rather than cleaning up postings made against an unfinished configuration.

Asset revaluations and impairments have no toggle; they post when the user posts them in Asset Management. Any automatic posting also needs an open fiscal period for the document date, as explained in our guide on fiscal year and period close in Skyline Nexus ERP.

• Auto-post Sales Transactions: final sales and sales returns; drafts, quotations and proformas are skipped
• Auto-post Purchase Transactions: purchases and purchase returns, including withholding-tax splits
• Auto-post Payment Transactions: customer and supplier payments, refunds and advances applied
• Auto-post Payroll Transactions: processed payroll
• Auto-post Expense Transactions: expenses and expense refunds
• Auto-post Depreciation Entries and Auto-post Asset Disposal Entries
• Auto-post Material Issues to GL: project material issues

Account mapping: telling each document where to post

The accounts a document hits are set in three layers. The first is General Settings, which holds the defaults: Default Cash Account, Default Bank Account, Default Accounts Receivable, Default Accounts Payable, Default Sales Account, Default Cost of Goods Sold Account, Default Inventory Account, Default Expense Account, the VAT Input Account and VAT Output Account, the asset and depreciation accounts, and the closing-entry accounts. The second is Settings, Account Mapping, with Sales Mapping (revenue, discount, returns, cost of goods sold, rounding), Purchase Mapping, Inventory Mapping, Payroll Mapping and Custom Mappings, explained on the Mapping Guide screen.

The third layer is the most useful for management reporting. Each product category can carry a GL Sales Account and a GL COGS/Purchase Account, and each expense category a GL Expense Account. When they are set, a single invoice's revenue and cost are split by product category automatically, which gives a gross margin by category in the ledger itself. An expense whose category has no GL mapping fails to post rather than being dropped into a default account, so an unmapped category shows up as an exception instead of a misstatement.

Testing the mapping before go-live

Posting rules deserve the same testing as any other control. Before switching the toggles on in the live business, post one example of each document type the business uses and inspect the journal each one produces, line by line, against the entry your accountant would have written by hand. Pay special attention to the documents that combine several rules: a sale with a discount, a mixed-category invoice, a purchase with withholding tax, a partial return and a payment that settles two invoices.

Write the expected entries down before you look at the result. Comparing against a written expectation catches the errors that pass a casual glance, such as discounts landing in revenue instead of a discount account, or rounding differences drifting into cost of goods sold. Keep the test file: it is the kind of evidence an auditor uses to understand automated controls and IT general controls under ISA 315 (Revised 2019), and it is the fastest way to re-test after a mapping changes.

• One cash sale, one credit sale, one sale with discount, one partial return
• One received purchase with VAT, one with withholding tax, one purchase return
• One customer receipt, one supplier payment settling two invoices
• One expense per expense category, one payroll run, one month of depreciation

Worked example: one POS sale across two categories

A coffee retailer in France sells, in one POS transaction paid in cash, coffee beans for EUR 400 and a grinder for EUR 1,200, both before VAT. At the French standard VAT rate of 20%, tax is 80 plus 240, EUR 320, and the customer pays EUR 1,920. The Beans category maps to sales account 4110 and cost account 5110, the Equipment category to 4120 and 5120. The consumed stock lots cost EUR 160 for the beans and EUR 780 for the grinder, tax-exclusive.

Because the sale was fully paid in cash at the POS, the debit goes to a cash-sales clearing account rather than to receivables. Output VAT is computed per line exactly as the tax reports compute it, so the VAT Output Account agrees with the VAT return. Revenue splits by category, and so does cost of goods sold, giving margins of 240 on beans and 420 on equipment in the ledger.

• Dr Cash-sales clearing 1,920 / Cr Sales - Beans 400 / Cr Sales - Equipment 1,200 / Cr VAT output 320
• Dr COGS - Beans 160 / Dr COGS - Equipment 780 / Cr Inventory 940
• Checks: 400 + 1,200 + 320 = 1,920; 160 + 780 = 940
• Margins: beans 400 - 160 = 240; equipment 1,200 - 780 = 420

Returns, credit notes and corrections

Two weeks later the customer returns the grinder. The return is recorded from List Sales Returns, where a return acts as a credit note and an invoice can have several partial returns. With sales auto-posting on, the return posts a reversing journal for revenue, VAT and cost: in the example, Dr Sales - Equipment 1,200, Dr VAT output 240, and Dr Inventory 780 with Cr COGS - Equipment 780, with the settlement side mirroring the original sale. The original invoice and its journal stay untouched, which is what an auditor wants to see.

Automatically generated journals belong to their documents. A posted journal created by a sale, purchase, payment, expense, payroll run, treasury voucher or stock transfer cannot be edited in the journal screen; you change the source document, and the posting follows. Deleting a payment reverses its journal. Once an invoice has been reported to or cleared by ZATCA, it is frozen and can only be corrected by a credit note or debit note. Our guide on how to cancel or correct a transaction compares each route.

Stock operations and their value in the ledger

Sales, purchases and returns carry inventory value into the ledger as shown above. Other stock operations are managed in the Inventory Control Centre. A stock transfer between locations moves quantities and cost between branches and does not create a journal, which leaves company inventory unchanged, as it should. Stock adjustments and opening stock have posting listeners that depend on a back-end setting, so confirm with your implementation contact whether they post for your business.

Where they do not, the value effect is a short manual journal. After a stock count finds EUR 350 of damaged stock written off through a stock adjustment, post Dr Inventory write-downs 350 / Cr Inventory 350 in the same period, and compare the Stock Valuation Report with the inventory account at month end. That comparison is the single most important reconciliation for any trading business, whatever the system.

Proving completeness: every document, one journal

Automatic posting shifts the accountant's job from typing entries to proving that every document posted once and correctly. Skyline Nexus ERP provides the tools under Fiscal Authority, Reports. Data Verification compares the trial balance, the general ledger transactions and the POS transactions. The Day Book offers a Gap Analysis, headed Audit Inspector on screen, which scans posted journals for broken links to their source documents and for amounts that do not match the source. Documents that never posted, typically because of a switched-off toggle, a missing mapping or a date in a closed period, show up when the POS transactions in Data Verification are compared with the GL transactions and when VAT Analysis is compared with the VAT Return form. All Transactions and All Payments give unified lists for audit review, and Transaction Mapping allows legacy manual mapping of transactions to accounts.

Run these before every month-end close, and investigate every gap rather than posting a balancing figure. A gap is information: it tells you which rule or setting failed, and fixing the rule fixes every future document.

• Data Verification: trial balance versus GL transactions versus POS transactions
• Day Book Gap Analysis: journals with a missing or mismatched source document
• VAT Analysis against the VAT Return form: VAT on the same basis from both sides
• Stock Valuation Report against the inventory account
• AR Aging Report and AP Aging Report against their control accounts

What still needs a manual journal

Automation covers transactions that have a document. Period-end judgements do not: accrued expenses without an invoice, prepayments spread over months, provisions, inter-branch allocations, foreign-exchange differences, and corrections. These are entered under Fiscal Authority, Journal Entries, New Journal Entry, with a Journal Date, optional Reference No., Description and at least two lines; total debits must equal total credits. Save as Draft keeps the entry editable, and Save and Submit sends it for approval when it is at or above the Approval Threshold.

Control flags on the chart of accounts keep manual journals honest. An account without Allow Manual Posting rejects manual lines, so leaving it unticked on the receivables, payables and VAT control accounts protects them from direct entries that would break their tie to the sub-ledger. Accounts flagged Requires Cost Center or Requires Party reject lines without a cost centre or a customer or supplier. Our guide on adjusting entries explains the period-end entries themselves.