We are restoring the requested view from its saved state. Your account and work remain unchanged while you wait.
Back to the track — ERP Systems Accountant
Sales requests a separate customer-advance account for every branch although the system already has a liability account and branch dimension. August reporting shows three unmapped accounts worth 184,000.00, two opposite-side balances worth 68,000.00 and a duplicate meaning worth 42,000.00. The team wants to open numbers today and add an other row to the report. Decide what needs an account versus dimension, govern and test the master, and hold release until mapping is complete.
Inside an ERP, numbering is not design. The chart defines stable economic meanings that survive staff, file and organisational changes. Begin with reporting, decisions and statutory needs, then derive the accounts required to produce them. A natural account says what the event is; company, branch, project, customer and cost centre describe where or for whom it occurred. Turning every dimension into another natural account makes the chart swell, destroys comparison and forces account migrations whenever the organisation changes. The first question is therefore not which number comes next, but which decision, control or disclosure genuinely requires a separate economic meaning.
Group entities may share an operating chart without sharing legal responsibility, ledger, period or currency. Design therefore identifies group and company layers, leading and parallel ledgers, transaction and presentation currencies, and the points where local treatment genuinely differs. The same cash account number in two companies does not create one balance; company, ledger and period remain part of its identity. A local requirement should not cause a copied chart when a governed local map, parallel ledger or attribute is enough. The practical test is whether each entity can be reported separately and consolidated without manual journals that erase source identity or mix transaction currency with presentation currency.
Electricity remains electricity whether incurred by a factory, office or project. Cost centre identifies responsibility, profit centre identifies business result, project or production order identifies purpose, and segment supports reporting. A separate electricity account for every site duplicates meaning and breaks history when organisation changes. Dimensions are not a dumping ground either: input tax, supplier liabilities, construction in progress and deferred revenue have distinct accounting and control and need appropriate natural accounts. Build a matrix stating where each information element belongs, who owns it and its source, then reject impossible combinations. Users choose governed values on each axis and reports compare them without post-export cleaning.
An account master is more than number and label. Record type, normal side, statement line, posting status, currency, open-item requirement, permitted tax handling, control-account relationship, mandatory dimensions and effective date. A currency-restricted bank account behaves differently from a multi-currency expense; a subledger control account should reject direct posting when customer or supplier detail must originate below it. A clearing account needs open-item identity and a clearing rule, while retained earnings is not a close-difference plug. Every attribute requires a rationale and a test. A plausible label with a wrong attribute can route thousands of balanced transactions into the wrong report, tax treatment or currency without stopping the journal.
The treatment starts from these documents. Follow the numbers to identify recognition date, amount, counterparty, reference and approval evidence before preparing the entry.
Facts and supporting evidence
The entity acquired an in-use machine for 180,000.00 on credit.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Plant and equipment | 180,000.00 | |
| Supplier payable | 180,000.00 | |
| Total (SAR) | 180,000.00 | 180,000.00 |
Treatment and financial effect
The use case is a capital asset and supplier remains in subledger.
Reperformance starts from this case's own facts: The entity acquired an in-use machine for 180,000.00 on credit. Obtain the original source that proves this event. The training drawings New account request, Account-map exception report explain field shape and reading order; they do not replace the case document or transfer their figures into it. Match entity, period, currency, reference and version to system configuration, master data, posting log and approval workflow, then confirm that the source supports the debit side (Plant and equipment) and the credit side (Supplier payable). Missing ownership, date, reference or approval remains an open exception; a balancing journal or undocumented assumption does not cure it.
Remeasure from the facts before reading the proposed journal, then add it independently: total debits 180,000.00 and total credits 180,000.00. Debit detail: Plant and equipment for 180,000.00. Credit detail: Supplier payable for 180,000.00. Link every line to the recognition or measurement rule explained in the lecture, then trace its reference and posting date. After posting, test module-to-ledger reconciliation, batch log and access roles. Equal sides prove arithmetic only, not the correct account, period or classification.
Before close, compare the correct treatment with the common alternative and record its specific effect: Assets are understated and expense overstated by 180,000.00, distorting profit and asset metrics. Do not close until the journal agrees with the extracted report, audit trail and close result and an independent reviewer can move from balance to account, reference and this event's own source. Keep the calculation, source version, journal identifier, reconciliation result and unresolved exceptions in the same workpaper. An attached file without a stated conclusion is not review evidence.
ERP stores effective-dated account master with owner, approval, type, normal side, currency, posting status, control relationship, dimensions, tax permissions and report map. Validation rejects invalid combinations, change log preserves versions, control accounts reject direct journals, and unmapped balances appear as exceptions before statement release.
Review account request 210420, define need, attributes, dimensions and map, then open 184,000.00 unmapped into evidenced decisions.
Work output: A workbook
These are yours once downloaded, and need no account. Fill them with your own figures and keep them in your portfolio.
Use the tool to test account balance against report line without treating equality as substitute for account attributes.
Turn an account request and incomplete map into governed release through eight decisions.
What you haveSales wants advance account per branch.
The arithmetic in this case runs in the tool itself, which is open to you any time with your own figures.
Log requests without decisions, duplicate meanings, missing attributes or effective dates, invalid combinations, direct control postings, unmapped accounts, historical rewrites and unreconciled loads.
This is not sent anywhere and not stored here. Write it down for yourself — in the workpaper you downloaded, or on paper.
The chart fixes natural meaning while dimensions carry company, centre and project. Account master governs side, currency, subledger, tax and map by effective date. No account or report releases before journal and map tests and zero unmapped balance.
How would you respond to a separate customer-advance account per branch while three accounts worth 184,000.00 remain unmapped?
Answer every question. Getting them all right records this lesson; you may retry as often as you need.
Reading alone records nothing.
The complete applied walkthrough is available below while the recording is prepared.
Team asks for customer-advance account per branch. I ask whether meaning changed: no; pre-service cash is one liability and branch is dimension. I govern 210420 as credit liability mapped to statements and block direct posting when customer identity is required. I test one allowed and one rejected journal and effective date. August's 184,000.00 unmapped is not put in other; open three accounts, repair maps or hold release. A small chart with strong meanings creates traceable reporting; more numbers move ambiguity to close.
A request saying a clearer account is needed is incomplete. It must state the expected event, why existing accounts and dimensions are insufficient, affected decision or disclosure, volume, frequency, entity, document type, dimensions, tax treatment, and sample journal and report. The chart owner searches for an existing account, dimension or reporting solution before creating one. An approved account receives a governed number, Arabic and English labels, attributes, effective date, affected processes, report map and test evidence. Test both an allowed posting and a combination the system must reject, then compare reports before and after. Creation of the master record is not release; production availability needs approvals, role updates and transition instructions.
A sound chart does not rely on user memory. Require cost centre for operating expense, asset order for project expenditure, customer for receivables control, and reject closed centres, unauthorised companies and incompatible tax codes. Validation rejects an invalid combination; substitution derives a reliable value from a known source. Do not use substitution to conceal missing input without informing the user. Give each rule an owner and test edge cases: foreign currency, a centre expiring mid-month, reversal, credit note and automated interface posting. A growing list of manual overrides signals a design or master-data problem, not a reason to grant every user a permanent bypass.
Do not edit a label, map or account status and silently reinterpret prior years. Every change needs effective date, reason, version, approver and affected population. Closing an account blocks new movements after a defined date but does not erase its balance or documents. A report-map change may require comparative rebasing and disclosure rather than replacement of an issued version. Distinguish request, approval, effective and first-use dates. Test transactions before and after the boundary, late postings into open periods and interfaces holding stale master data. The change log must answer who changed what, when and why, who tested the effect, and which reports, roles and import templates were reissued.
Supplier payables in the general ledger should originate from supplier items, customer receivables from customer items and fixed-asset balances from asset records according to system design. Direct posting to a control account can leave the ledger correct in total while the subledger is wrong, removing counterparty, age and clearing identity. Correct the source event or use a tightly restricted exception route that retains party, reference and approval and restores the tie. Reconcile control account to subledger by company, currency and period, opening differences to documents rather than one net number. Agreement does not prove every item, but it proves the layers have not separated; disagreement stops close and reporting until explained.
Every posted account must reach a statement line, note, normal side and appropriate classification under an owner and effective date. An unmapped account must not disappear into other or fall out because an Excel row was not added. Test mapping for debit and credit balances, zero balances with large movement, and current or non-current portions whose classification comes from maturity evidence rather than account name. Mapped totals must equal the same-version trial balance, with unmapped and exception amounts visible. When a map changes after a new account or journal, rerun statements, ratios and notes from source and withdraw the prior version instead of editing presentation cells to make the report appear balanced.
During migration, do not move every legacy account merely because it once held a balance. Classify accounts as active, replaced, closed or duplicate and map each old value to a new one through an explicit conversion rule. Separate opening balances from historical movements and preserve party, currency, open-item identity and dimensions. Rehearse the load, compare count, debit, credit and net by entity, currency and account, and resolve rejected rows through a log rather than deletion. Prevent parallel use of old and new charts after cutover and define the late-transaction route. A file accepted by the loader is not success; success is source-equivalent reporting and traceability from balance to understandable document and valid authority.
Stop creation when the need is a temporary project, supplier name, campaign, location or narrative that belongs in a governed dimension or reference. Stop when there is no owner, report map, sample journal or expected volume, or when the proposed account would be used once to hide a difference. A time-bound project code, analytical value or detailed report can replace a permanent natural account when the data remains governed and extractable. If the account is necessary but tax, currency or posting authority is unresolved, hold the request rather than release defaults. A smaller chart with strong meanings is safer than thousands of numbers that move ambiguity from the posting screen to month end.
Facts and supporting evidence
The entity received 75,000.00 from a customer before service.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Cash at bank | 75,000.00 | |
| Customer advances | 75,000.00 | |
| Total (SAR) | 75,000.00 | 75,000.00 |
Treatment and financial effect
Natural account is performance liability; branch remains a line dimension.
Reperformance starts from this case's own facts: The entity received 75,000.00 from a customer before service. Obtain the original source that proves this event. The training drawings New account request, Account-map exception report explain field shape and reading order; they do not replace the case document or transfer their figures into it. Match entity, period, currency, reference and version to system configuration, master data, posting log and approval workflow, then confirm that the source supports the debit side (Cash at bank) and the credit side (Customer advances). Missing ownership, date, reference or approval remains an open exception; a balancing journal or undocumented assumption does not cure it.
Remeasure from the facts before reading the proposed journal, then add it independently: total debits 75,000.00 and total credits 75,000.00. Debit detail: Cash at bank for 75,000.00. Credit detail: Customer advances for 75,000.00. Link every line to the recognition or measurement rule explained in the lecture, then trace its reference and posting date. After posting, test module-to-ledger reconciliation, batch log and access roles. Equal sides prove arithmetic only, not the correct account, period or classification.
Before close, compare the correct treatment with the common alternative and record its specific effect: Liabilities are understated and profit overstated by 75,000.00. Do not close until the journal agrees with the extracted report, audit trail and close result and an independent reviewer can move from balance to account, reference and this event's own source. Keep the calculation, source version, journal identifier, reconciliation result and unresolved exceptions in the same workpaper. An attached file without a stated conclusion is not review evidence.
Facts and supporting evidence
A recoverable employee advance of 18,000.00 was paid.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Employee advances | 18,000.00 | |
| Cash at bank | 18,000.00 | |
| Total (SAR) | 18,000.00 | 18,000.00 |
Treatment and financial effect
Entity holds employee claim; centre is a dimension, not expense.
Reperformance starts from this case's own facts: A recoverable employee advance of 18,000.00 was paid. Obtain the original source that proves this event. The training drawings New account request, Account-map exception report explain field shape and reading order; they do not replace the case document or transfer their figures into it. Match entity, period, currency, reference and version to system configuration, master data, posting log and approval workflow, then confirm that the source supports the debit side (Employee advances) and the credit side (Cash at bank). Missing ownership, date, reference or approval remains an open exception; a balancing journal or undocumented assumption does not cure it.
Remeasure from the facts before reading the proposed journal, then add it independently: total debits 18,000.00 and total credits 18,000.00. Debit detail: Employee advances for 18,000.00. Credit detail: Cash at bank for 18,000.00. Link every line to the recognition or measurement rule explained in the lecture, then trace its reference and posting date. After posting, test module-to-ledger reconciliation, batch log and access roles. Equal sides prove arithmetic only, not the correct account, period or classification.
Before close, compare the correct treatment with the common alternative and record its specific effect: Assets and profit are understated by 18,000.00 and collection item disappears. Do not close until the journal agrees with the extracted report, audit trail and close result and an independent reviewer can move from balance to account, reference and this event's own source. Keep the calculation, source version, journal identifier, reconciliation result and unresolved exceptions in the same workpaper. An attached file without a stated conclusion is not review evidence.
Facts and supporting evidence
The bank charged an actual service fee of 6,400.00.
Correct treatment and entry
| Account | Debit | Credit |
|---|---|---|
| Bank charges | 6,400.00 | |
| Cash at bank | 6,400.00 | |
| Total (SAR) | 6,400.00 | 6,400.00 |
Treatment and financial effect
Account describes bank service and maps to proper expense line.
Reperformance starts from this case's own facts: The bank charged an actual service fee of 6,400.00. Obtain the original source that proves this event. The training drawings New account request, Account-map exception report explain field shape and reading order; they do not replace the case document or transfer their figures into it. Match entity, period, currency, reference and version to system configuration, master data, posting log and approval workflow, then confirm that the source supports the debit side (Bank charges) and the credit side (Cash at bank). Missing ownership, date, reference or approval remains an open exception; a balancing journal or undocumented assumption does not cure it.
Remeasure from the facts before reading the proposed journal, then add it independently: total debits 6,400.00 and total credits 6,400.00. Debit detail: Bank charges for 6,400.00. Credit detail: Cash at bank for 6,400.00. Link every line to the recognition or measurement rule explained in the lecture, then trace its reference and posting date. After posting, test module-to-ledger reconciliation, batch log and access roles. Equal sides prove arithmetic only, not the correct account, period or classification.
Before close, compare the correct treatment with the common alternative and record its specific effect: Revenue and bank expense are both understated by 6,400.00 and classification is wrong. Do not close until the journal agrees with the extracted report, audit trail and close result and an independent reviewer can move from balance to account, reference and this event's own source. Keep the calculation, source version, journal identifier, reconciliation result and unresolved exceptions in the same workpaper. An attached file without a stated conclusion is not review evidence.