Chart of Account

Every journal in BigLedger posts into the GL codes defined here. Map the company’s Default GL Codes before anyone finalises a document: an invoice cannot post to the General Ledger until they are mapped, and nothing can be dated into a fiscal period you have locked.

Overview

The Chart of Account applet defines the structure every journal in BigLedger posts into: GL Sections (Assets, Liabilities, Equity, Revenue, Expenses), GL Categories within them, and the GL Codes that transactions actually hit. It also holds, per Company, the ledgers, the Default GL Codes that tell sales, purchase, stock, forex and consignment documents which accounts to post to automatically, the Sets of Books, the Fiscal Years whose periods can be locked, and the month-end Closing Stock Balance values the Profit and Loss report uses.

It is opened by the finance administrator during implementation and by the accountant at month-end. It sits before every posting document: an invoice cannot post to the General Ledger until the company’s default GL codes are mapped (FINAL still goes through; the posting job behind it is what fails). Its date is checked too: it cannot be finalised with a date in a period locked for transactions.

    flowchart TD
  COA["Chart of Account"] --> SEC["GL Section<br/>Assets, Liabilities, Equity, Revenue, Expenses"]
  SEC --> CAT["GL Category<br/>Current Assets, Fixed Assets, Trade Debtors, ..."]
  CAT --> CODE["GL Code<br/>the account a transaction posts to"]
  CO["Company<br/>assigned a chart in Organisation"] --> COA
  CO --> LED["Ledger<br/>PRIMARY / SECONDARY / CONSOLIDATED"]
  CO --> FY["Fiscal Year"]
  CO --> DEF["Default GL Codes<br/>which account each document type posts to"]
  DEF --> CODE
  LED --> SUB["Sub-ledger<br/>created when a default GL code is saved;<br/>journals and opening balances land here"]
  FY --> PER["Fiscal Period<br/>OPEN / LOCK_GL / LOCK_TXN / LOCK_ALL"]
  SOB["Set of Books<br/>what financial reports run against"] --> LED
  

Where it fits

Modules: Core, Financial Accounting.

Screens and menus

Gear (Settings) menu, group System Configuration: General Settings, Field Settings, Default Selection, plus the shared Webhook, Feature Visibility, permission and Release Notes screens. Personalisation menu: Default Selection (per user).

Chart of Account (tree view)

Screenshot withdrawn; a recapture from a demo tenant is on the list.

Drill from Section to Category to Code, search, create a new chart, or delete one (with confirmation). A tenant normally has one chart; several are possible when companies keep different structures.

New does more than save a header. It seeds 18 report sections, their categories and 200 GL codes with numeric account numbers from the built-in default (the Organisation applet’s + next to Chart of Account does the same) — every section, category and code is listed under The built-in template. A new chart is therefore never empty; rename or deactivate what you do not need rather than expecting a blank tree.

Besides Details, GL Code Link and GL Code, the chart carries four tree tabs — Segment, Dimension, Profit Center and Project.

They are not four names for the same thing, and you do not have to choose between them. All four are separate tags on the journal line and on the document line, and journal posting copies every one of them from the document onto the line it writes. Branch is a fifth tag again, independent of all four. So one sale can be tagged Retail and Klang Valley and the Q4 campaign and the refit project at once, and be cut four different ways afterwards.

That is why a chart should not grow a code per branch or per business line. Twenty-two branches by forty product lines is 880 GL codes maintained forever, recreated every time a shop opens — and you would still have no way to cut revenue by business line, because you would have spent the dimension on the branch you already had for free. Keep one SALES-SMARTPHONE and let the tag carry the cut. The exception is cash and bank: CASH-PRI-KV01 is a separately reconciled balance, not a slice of one, and earns its own code.

What it will not do: the chart does not require a tag. A document applet can — the Sales Invoice applet’s Field Settings can make each of the four compulsory on the line — but where none is required and a profit centre is left blank on both the document line and its header, the journal line is written with it blank too, and the figure lands in the unallocated remainder of every profit-centre report from then on. It is not repaired retrospectively — the tag is copied at posting time, not looked up at report time.

Tab order is configurable (CHART_OF_ACCOUNT_DETAILS_TAB_ORDER, see Configuration).

Screenshot withdrawn; a recapture from a demo tenant is on the list.

Segments, dimensions, profit centres and projects share one shape: a Code (immutable), a Name, an optional Description, an optional Parent (select No Parent for the top level), a Status, and Ref 1 – Ref 5 (code, name, description) for extra tagging. Use them instead of duplicating GL codes per branch: keep one EXPENSE-RENTAL and tag the profit centre.

Where a journal line’s tag comes from, and what the profit report does with it

• The document line first, then the header. When a document posts, each goods, tax and charge line of the journal takes the segment, dimension, profit centre and project on its document line, and where the line is blank, the header’s. The customer or supplier line, and a foreign-exchange gain or loss line, always take the header’s. On a sales invoice line, the Department tab’s Copy from Hdr tick fills the line from the header while you enter it. Leave it unticked and the line blank, and the journal still carries the header’s tag.
• Cost of sales does not fall back. The Financial Report applet’s Profit Loss Report takes revenue and expenses from journal lines, which carry that fallback. It computes cost of goods sold from the sales document lines themselves, which do not. Suppose GadgetSphere Distribution invoices 40 laptops at RM 3,200 with the project set on the header only. Grouped by project, that column shows RM 128,000 of sales and no cost, where the stock cost RM 108,000. The column’s margin reads 100%, and the RM 108,000 is missing from the report’s total cost too. Nothing on the screen tells you a cost was left out.
• One tag at a time. The report groups by branch, GL dimension, segment, profit centre or project, and shows the picker for that one only. You cannot ask for one project within one segment.
• Every company at once. Grouped by anything but branch, the report has no company filter. If GadgetSphere and GadgetSphere Distribution tag the same project, the column adds both companies' journals. That is what you want for a group-wide project, and not what you want for one company’s figures.
• The tree does not add up. The Parent field arranges the tree tab, but the report counts a line only under the value it was tagged with. Ticking a parent in the report does not bring its children’s lines in.

GL Section, GL Category, GL Code

GL Sections come pre-populated when the chart is created (see Chart of Account (tree view)). You can rename them (Name, Account No.) and add more, but the section codes are a fixed vocabulary that the financial statements key on: eleven P&L codes (SalesRevenue, SalesExpenses, CostOfGoodsSold, CostOfGoodsSold-Gains, CostOfGoodsSold-Expenses, GeneralExpenses, OtherRevenues, OtherExpenses, TaxExpenses, Dividend, ProfitLoss) are closed to profit and loss at month-end; every other section code is carried forward as balance sheet. The template seeds ten of the eleven — Dividend is not created; a section with exactly that code is closed to profit and loss if you add one. The applet’s own opening-balance report keys on CurrentAssets, FixedAssets, CurrentLiabilities, LongTermLiabilities, ShareCapital, RetainedEarnings and the P&L codes.

A GL Category has a Details tab (code — read-only after creation — name, description, account no., Include for MITRS, and on Edit only a parent category; there is no chart of account, because a category belongs to none), a GL Code tab where codes can be created with the category pre-selected, and a GL Section tab that links the category to its section. On screen a category is created first and linked to a section on the GL Section tab; the CSV import links each row to its section in the same pass by SECTION_CODE (see Import GL Category / Import GL Code).

A GL Code has a Details tab and a Chart of Account Link tab (one code can belong to more than one chart).

The built-in template

Every new chart (the applet’s New, and the Organisation applet’s +) is seeded from one built-in template of 200 rows, each naming a section, a category and a GL code, which writes 18 GL Sections, 53 GL Categories and 200 GL Codes. What lands where:

The template is product seed data, transcribed below exactly as the source spells it (names, capitalisation and spelling included) so that what you read here matches what the GL Section, GL Category and GL Code screens show on a fresh tenant. Sections are listed in account-number order. Codes marked Fixed are the ones the reports key on by code: the eleven P&L codes (ten of them are seeded — Dividend is recognised but not created by the template) and RetainedEarnings, which retained-earnings processing and the opening-balance report both read by code. The remaining balance-sheet codes are also in that layout; rename any section’s Name, never its Code.

Deactivating template codes you do not use. Setting a seeded GL code to INACTIVE (GL Code > Details > Status; the only other value offered is ACTIVE) is a listing-side change, not a posting-side one. The applet’s own listings — GL Code, the chart’s GL Code tab, the category’s GL Code tab, the chart-link tabs — show ACTIVE codes only, so the code drops out of them; the GL Code listing’s advanced search has a Status filter that brings it back when you need to edit or reactivate it. The journal-line selector in Ledger and Journal also lists ACTIVE codes only, so an inactive code cannot be picked on a manual journal line — but Import Journal in the same applet matches each row’s GL code by its code and accepts an inactive one, and so does the journal API. The item-level GL selector on sales and purchase lines does not filter on status — an inactive code is still selectable there. Posting never looks at the status: a Default GL Code or an item-company link that points at an inactive code still posts through it, and month-end and the statements apply no status filter either, so history posted to an inactive code stays in every report. Deleting is not an alternative once the code has been used (see Troubleshooting); GL Code Merge moves the history if you want the code gone from the listings and the statements alike. The same ACTIVE-only listing rule applies to seeded sections and categories — and an inactive category still carries its section link, so its codes keep classifying.

Companies

Every ACTIVE company of the tenant is listed here — a company without a chart still appears, with an empty chart column. What the chart of accounts gates is the Default GL Codes tab, not the listing.

• Main — Company Code (read-only), Company Name, Registration No., Currency, Tax ID, SST ID, Chart of Account, Inventory Cost Base On.
• Ledgers — create ledgers (Code, Name, Type PRIMARY / SECONDARY / CONSOLIDATED, Currency). Clicking a ledger opens its sub-ledger listing with an Opening Balance tab (primary ledgers only) and a Remove Journal tab.
• Fiscal Year — the fiscal years of this company. When at least one Closing Stock Balance toggle is on (see Configuration), clicking a year opens the Closing Stock Balance screen: one tab per stock class (Inventory, Raw Material, WIP, Finished Goods, NSTI), each a month-by-month grid of Stock Value (System), Stock Value (Manual), Select System and Select Manual. The Inventory tab also has a BASE ON cost-basis selector (MA_COST, WA_COST, FIFO_COST, LIFO_COST, REPLACEMENT_COST, MANUAL_COST).
• Default GL Codes — the mapping table that lets documents post automatically (see Configuration). Shown only when the company has a chart of accounts.

Set of Books

A set of books groups one or more ledgers for a reporting purpose (statutory, management, consolidation). Details holds the name; Ledgers links existing company ledgers (each link shows the ledger’s code, type, name and currency read-only, with a Delete to unlink).

Screenshot withdrawn; a recapture from a demo tenant is on the list.

Fiscal Year and Fiscal Periods

Screenshot withdrawn; a recapture from a demo tenant is on the list.

Create a fiscal year with Company, Name, Start Date and End Date; the screen generates one period per calendar month, snapping the start to the first of its month and the end to the last. Only the screen is monthly — periods created through the API can be any length. The year itself has a status of ACTIVE or CLOSED; each period has a Closing Status of OPEN, LOCK_GL, LOCK_TXN or LOCK_ALL (see Lifecycle). Click a period row to open Fiscal Period Details, change the status and Save. The year’s Main tab also carries a two-click DELETE.

Import GL Category / Import GL Code

Download the *Sample Format CSV from the import screen, fill it, drag-and-drop or upload, review the row flags (green = ready, red = error, hover for the reason) and click ADD.

Import GL Category serves MasterData_Upload_GLCategoryData.csv with columns GL_CATEGORY_CODE | GL_CATEGORY_NAME | PARENT_CATEGORY | DESC | ACCOUNT_NO | SECTION_CODE. Each row is linked to the report section whose code is SECTION_CODE; an unknown code fails the row with INVALID SECTION CODE.

Import GL Code serves MasterData_Upload_GL_Code.csv with columns CHART_OF_ACC | GL_CATEGORY | GL_CODE_1 | GL_NAME | DESC | GL_CODE_3 — CHART_OF_ACC is the chart’s code and GL_CATEGORY is the category code (not its name; failure text GL Category is invalid). A row whose GL_CODE_1 already exists in that chart updates the existing code’s name, category and description instead of failing.

GL Code Merge

Choose the chart, the category, the Source (duplicate) code and the Target (surviving) code, click MERGE and confirm. All history moves to the target and the source is deactivated. Both codes must be in the same GL Category.

GL Code Create Item

Select a GL Category, SEARCH to list its GL codes, CREATE to generate one Account Code item per GL code in Doc Item Maintenance. Sales staff can then invoice “Consulting income” as a line and the revenue lands on the right account.

Configuration

Before you can use it

Recommended setup order: verify the company → create ledgers → build (or import) sections, categories, codes → map Default GL Codes → create a set of books and link the ledgers → create the fiscal year.

Who owns the chart, and how the codes are numbered

The chart decides how the business will be read for years, so it is one person’s decision rather than everybody’s data entry. In a group like GadgetSphere that is the group finance manager, and a new code goes through them. Two facts make the friction worth it. A GL Category is shared by every chart on the tenant (see GL Category — Details), so renaming one for GadgetSphere Distribution renames it for GadgetSphere and GadgetSphere Online as well. And near-duplicate codes are how a ledger splits: staff pick whichever of two similar names they see first, and deleting the “wrong” one later strands every document that used it (see Troubleshooting). The owner’s own check is to read the GL Code listing once a month for codes nobody approved.

Each GL code carries two identifiers: the GL Code itself and the Account No. beside it. The built-in template uses both — a word-like code such as cashOnHand with the six-digit account number 110102 — so a word in GL Code and a number in Account No. is the shape a new chart starts with. The numbering decision is really two, and both conventions are defensible:

• A mnemonic code with the number beside it — SALES-SMARTPHONE in GL Code, a six-digit number in Account No. The code reads on every journal line, import file and picker without a lookup, and the number keeps the order your accountant and auditor expect. This is the convention the wiki’s guides use.
• A numeric code — 4100 in GL Code. Familiar to an accountant trained on numbered charts and easy to map to an auditor’s template; the cost is that a journal line or an import row needs the name beside it before anyone can read it.

Either way, settle it before the first import, because Import GL Code finds an existing code by its GL Code text. The Edit screen does accept a new GL Code, and the history follows the account (postings point at the account, not at its text), but a renamed code no longer matches the CSV you keep, and the server does not check a renamed code against the rest of the chart. Neither convention needs the branch in the code: the branch is already a column on every journal line (see Chart of Account (tree view)). Cash and bank are the exception — CASH-PRI-KV01 is a separately reconciled balance and keeps its suffix.

Applet settings

All three Settings screens save tenant-wide, so a change applies to every user of the applet. The Personalisation > Default Selection screen saves per user. Anyone who can open the applet’s gear menu can change them: the applet registers no permission definitions (see Feature visibility / permissions).

Settings > General Settings

The toggles only govern screen visibility inside this applet; no report reads them. What the Profit and Loss report reads is the data entered on those tabs — see Lifecycle and effects.

Rendered but not consumed. The Default GL Code text area on the same screen is saved and read by nothing. It has no effect on posting or on new charts; leave it empty.

Settings > Default Selection

Rendered but not consumed. The same screen offers Default Branch / Default Location pickers, and the Personalisation > Default Selection screen stores the per-user pair. No screen in this applet reads them — the applet has no branch- or location-scoped listing.

Settings > Field Settings shows eight slide toggles (Unit Discount, SST/VAT/GST, WHT, Blanket Order, Segment, G/L Dimension, Profit Center, Project). None is bound to a form control or a stored key; the screen has no effect.

Companies > Default GL Codes — the mapping that matters most. Each key takes exactly one GL code from the company’s chart; saving stores the mapping and, if the primary ledger has no sub-ledger for that GL code yet, creates one and links it:

Screenshots (the General tab capture is pending a recapture): Entity · Sales · Purchase · Stock · Forex · Consignment

Document behaviour settings

Not applicable — the applet maintains master data and has no document status flow of its own. Posting behaviour is governed by the Default GL Codes and fiscal period locks described here, not by document switches.

Feature visibility / permissions

This applet has no client-side permissions and no SHOW_* / HIDE_* checks. Access is controlled by installing the applet for a user; there is no per-tab or per-menu permission inside it. The only conditional screen is the Default GL Codes tab, which renders once the company has a chart of accounts.

Fields

GL Code — Details

A GL code also takes a GL Name (required) and an optional Description and Account No., each capped at 255 characters and read by nothing but the reports that print them. The rows below are the ones that fail, block or change something.

GL Category — Details

A category takes a GL Category Name, an optional Description and Account No., and — on the Edit screen only, not on Create — an optional GL Category (parent). The parent is stored and read by no report: a sub-category is not rolled up into its parent anywhere, so if you want a sub-total, make it a category of its own under the section.

A category belongs to no chart. Neither the Create nor the Edit screen offers a Chart of Account, and the category record has nowhere to keep one. Every chart on the tenant shares the same categories; it is the GL code that ties a category to a chart. So if GadgetSphere keeps a second chart for its distribution company, renaming a category or changing its MITRS flag changes it for both charts at once. To give one company a different grouping, create a new category with its own code and move that company’s GL codes into it from the GL Code screen.

Chart of Account, Segment, Dimension, Profit Center, Project

The shape is described under Screens and menus above: a Code that cannot be changed after creation, a Name, an optional Description, a Status that can be, and — on the four trees but not on the chart itself — an optional Parent and Ref 1 – Ref 5. Nothing on these five screens validates against anything else, and nothing outside them reads the Ref fields.

Company — Main

The identification half of this tab — Company Code (read-only), Company Name, Company Registration No., Currency, Tax ID#, SST ID# and the audit stamps — is stored and printed and changes nothing else. Two fields on it decide how the company’s numbers come out.

Company — Ledger

A ledger takes a Ledger Code, a Ledger Name and a Currency. The one field that changes what you can do with it is the type.

Company — Ledger detail (sub-ledger listing)

Company — Default GL Codes

Company — Closing Stock Balance (per fiscal year, per stock class)

One row per fiscal month, per stock class.

Set of Books

Fiscal Year / Fiscal Period

Each period carries an editable Period Name, Start Date and End Date.

Lifecycle and effects

Chart of account records do not post; they are the targets of posting. The applet nevertheless writes four things other applets depend on, and controls when posting is allowed.

What it writes

Fiscal period locks. The backend checks the period of the document’s or journal’s transaction date for its company:

Two document types are explicitly exempt from LOCK_TXN / LOCK_ALL: outbound and inbound stock transfers — Stock Transfer documents can still be finalised into a locked period.

Reopening is done by setting the period back to OPEN; there is no separate approval step in the applet, so restrict who can install it.

What one FINAL sets off, and where the default GL codes are read

FINAL on a sales or purchase document saves the status and queues one job; the screen comes back before the journal exists. The journal job then reads this company’s Default GL Codes as they stand when it runs, not as they stood when the document was drafted, and builds the journal in three steps:

1. It looks up the company’s primary ledger and its default GL codes. A company with no primary ledger, or with no default GL code mapped at all, stops the job before anything is built.
2. Each goods, tax and charge line looks for its account — line, header, item, company default; tax takes the company default only. A line that finds none is left out, and nothing fails (FACT-0006).
3. The customer’s or supplier’s line is built from whatever the kept lines add up to, and a missing default for it stops the journal. Which default it asks for comes from that party’s AR/AP Type for this company: the row on the customer’s or supplier’s Company Linking tab where one exists, the type on the record itself otherwise. A trade receivable asks for the trade debtors default, an other receivable for non-trade debtors, a merchant receivable for merchant receivable; a trade payable for creditors, an other payable for non-trade creditors, a merchant payable for merchant payable, and an employee for employee other payable. The mapping is asked for only on a document that needs a receivable or payable line — one whose kept lines add up to something other than zero.

Because the type is read per company, one supplier can sit in two different payable accounts: a distributor that is a trade creditor of GadgetSphere Distribution, and from which GadgetSphere buys only shop fittings, can be a non-trade creditor of GadgetSphere — set once on the Company Linking tab, with no second supplier record.

What the defaults touch elsewhere. Every posting document reads them. A receipt’s or payment’s money line posts to the GL code of the cashbook its settlement method names, so a cashbook with no GL code fails that journal (see Troubleshooting). Month End Processing reads the cost-of-sales, stock, purchase, profit-and-loss and retained-earnings defaults when it closes a month (what each one does there). A sales invoice’s own journal carries no cost of sales; that is written at the month-end close.

Changing a default later changes the journals posted from then on, and none already written. Repost on Trace Document rebuilds a document’s journal with the defaults as they are that day. That is how you re-route a document posted to the wrong account, and why you should not Repost a document in a month already reported: its journal changes under the report.

Where the figures come from

• Live: a document’s Journal Txn grid, the journal listings in Ledger and Journal, and the ad-hoc Profit Loss Report read posted lines as you open them.
• A manual journal is final the moment Create succeeds. There is no draft: the server refuses it unless debits equal credits, gives it a posting number and posts it in the same step.
• Stored: the Trial Balance, Profit and Loss and Balance Sheet of a Financial Report snapshot read a monthly summary of each account, and that summary is written only when Month End Processing creates or processes a month. A journal dated into a closed month reaches the statements only after that month and every later one are processed again and the snapshot is regenerated — and that includes the go-live figures you key on the primary ledger, which are a journal too, so close the month they are dated in first.

Closing a period: whose job it is, and how they know it is closed

The product holds the lock; deciding when a month is finished is the accountant’s job. The four statuses fit a close that happens in stages. Locked for transactions, a month stops taking invoices and vouchers while the accountant still makes adjustments by journal — the shops are already trading in April, the books for March are still being finished. Locked for the general ledger is the reverse: documents still flow while hand-keyed journals stop, for example while an outside reviewer reads the month’s journals. Locked for everything is the month closed.

A workable order for GadgetSphere at each month-end:

1. Clear the month. Ledger and Journal’s Missing Journal listing shows nothing for its dates (for the document types it lists), and the bank and cash GL codes are tied to their cashbooks (how).
2. Lock the period for transactions, post the adjustments, then run Month End Processing for each Set of Books. The lock does not stop Month End Processing — its journals are written by the close itself — so locking first is safe.
3. Lock the period for everything once the statements are read.

Three things a lock does not hold, which is where the close owner has to look:

• Repairs. Resolve and Repost on Trace Document post on the document’s own date whatever its period says, so a document repaired after the close changes the locked month. Re-run Month End Processing for that month and every later one, and regenerate the snapshot.
• Edits and clones of manual journals (see the lock table above). An existing manual journal can be re-dated or changed with UPDATE inside a locked month. Two defensible ways to correct a mistake follow from that, and the choice is yours: correct it in place with UPDATE, which keeps one entry but changes a month somebody may already have reported; or post a correction journal in the open month, which leaves the original and the fix both on record at the cost of two entries (Journal entries walks both).
• The year’s own status. Closing a fiscal year locks nothing; locking every period of it does (see Fields).

Reopening is one change of status with no approval step, so the person who closes the month should not be the person who posts into it, and anyone who reopens a period should say why to whoever owns the close.

How you know the set-up is right

Run this once per company after mapping the defaults, and again after any change to them.

1. Post one real sale and read its journal. Finalise a sales invoice for a laptop at RM 2,000 plus RM 120 SST to a customer whose AR/AP Type is trade, then open the invoice’s Journal Txn. Right: three lines — debit your trade debtors account (DEBTOR-TRADE-RETAIL) RM 2,120, credit the laptop’s sales account (SALES-LAPTOP) RM 2,000, credit LIAB-SST-OUTPUT RM 120. A debtor line of RM 120 and no sales line means neither the item nor the company has a sales code. A debtor line of RM 2,000 and no tax line means the company’s output tax default is unmapped. An empty grid that stays empty means the job failed: Resolve on Trace Document’s Missing Journal shows why. There is no cost-of-sales line, and there should not be one.
2. Try a journal into a locked month. In Ledger and Journal, create a manual journal dated in a month you have locked for the general ledger or for everything. Right: The selected date falls within a locked fiscal period, and no journal.
3. After the first close, tie a control account. The trade debtors GL code on the Trial Balance should equal the debtor ageing at the same month-end. A past month’s ageing is a stored copy taken by a scheduled job, and one that ran late holds the balances of the day it ran rather than the month-end’s, so a difference can be the copy’s age; a difference of exactly a sales or tax amount points back to step 1.

Related applets

• Organisation — creates companies and branches and assigns each company its chart of accounts.
• Ledger and Journal — manual journals against these GL codes; subject to LOCK_GL.
• Financial Report — trial balance, P&L and balance sheet by set of books; the P&L reads the company’s cost basis and the Closing Stock Balance selections made here.
• Cashbook — every cashbook maps to a bank or cash GL code.
• Tax Configuration — tax codes whose document lines post to the INPUT_TAX / OUTPUT_TAX defaults.
• Doc Item Maintenance — Account Code items generated by GL Code Create Item; the item-company GL link is the third step of the GL precedence.
• Customer Maintenance and Supplier — the entity’s AR/AP type decides which DEBTOR* / CREDITOR* default is used.
• Stock Transfer — the one document family that bypasses LOCK_TXN / LOCK_ALL.

Troubleshooting

Related documentation

• Chart of accounts setup guide — the walkthrough for a new tenant.
• Financial Accounting module and Opening balances.
• Core module.