Anatomy of the CoA

The CoA sheet is organized into 13 columns (A through M). Each column serves a specific functional purpose. Click “More...” to view the detailed logic for each level.

Modifying your CoA

While Abaque provides professionally designed templates, your initial configuration will likely involve a combination of manual account adjustments and high-level structural alignment to mirror your specific business model. In this section, we cover the essential operations for managing your ledger's lifecycle and the specific configuration required for agricultural and non-agricultural operations.

1. Account Lifecycle

To maintain the structural integrity of the Abaque engine, all modifications to the CoA must follow specific mechanical rules. Because balances and dropdown menus rely on contiguous ranges and ascending numeric logic, it is important to follow these rules during the editing process.

Adding New Accounts

When expanding your ledger, never add rows to the very bottom of a section. Instead, always insert a new row between two existing accounts.

• Sequential Integrity: The Abaque engine requires all account numbers to be entered in strictly ascending numerical order. If a new account is added out of sequence, the GIFI_21_BALANCE function will return a validation error.
• Journal Eligibility (Dropdown Sync): After entering the GIFI Code, Account Number and Name, you must determine where the account should appear in the Journal. Refer to the Anatomy of the CoA table above for the specific “Account Eligibility Rules” regarding Debit (Col G) and Credit (Col H) availability.
  • To make an account selectable, copy the concatenation formula from an adjacent row into the appropriate column. This formula dynamically references the data in that specific row (i.e., =$E<row> & " " & $F<row>) to create the entry string used by the Journal.
  • To restrict an account, leave the corresponding cell blank. For instance, to prevent an Expense from appearing in the Credit list, leave Col H blank.
• Categorical Logic: Inserting the row in its correct numerical position ensures that the Journal dropdown menus remain intuitive, placing the new account exactly where it belongs within its functional category (e.g., placing a new Bank account near existing Cash assets).

Modifying Existing Accounts

You can safely rename, albeit with some caveat, an account (Col F) or change its classification at any time. However, Account Numbers (Col E) must never be changed once transactions involving them have been recorded in the Journal or if they carry a balance from the previous year.

• The Structural Link: Abaque uses the Account Number as the primary key to link Journal entries to the CoA. If you change a number that is already in use, the engine will trigger a validation error because the original account number used in a transaction can no longer be found.
• Renaming & Data Validation: If you change an account name in the CoA, the Abaque engine continues to calculate balances correctly. However, because the Journal uses Data Validation ranges, existing entries will show an “Invalid: Input must fall within specified range” error. To clear these flags, you must re-select the updated account name from the dropdown menu for those specific transactions.
• Carryforward Impact: The GIFI_BALANCE_CARRYFORWARD function relies on matching account numbers between fiscal years. If you renumber an account that held a balance last year, the engine will be unable to “roll over” that amount to the new year, resulting in a “cannot carry over” error.
• GIFI Reclassification Guardrails: While you can update an account's GIFI Code (Col D), it must remain compatible with its Account Number block. The Abaque engine enforces strict mapping rules (e.g., Short Term Assets must stay within the 1000-1486 range). Refer to the Account Range & GIFI Mapping table below for permitted ranges.

Deleting or Removing Accounts

Deleting an account is a permanent action. Never simply clear the contents of a cell; you must manage the entire row to maintain the engine's structural integrity.

• Historical & Carryforward Data: Before deleting a row, you must ensure the account has a 0.00 balance in the current year and no closing balance from the previous year. If you delete an account that carries a balance forward from a prior fiscal year, the engine will return an error stating that the balance cannot be moved to the new year as the destination account no longer exists.
• The "Delete Row" Command: To remove an account, you must delete the entire row (Right-click the row number > Delete Row). This allows Google Sheets to shift the remaining accounts up, preserving the contiguous range and sequential logic required by the GIFI_21_BALANCE function across the CoA.
  • Special Handling for Anchor Rows: If the account you wish to remove is the top row (anchor) of a merged section in Columns A, B, or C (such as Row 3 for the Balance Sheet, Assets, and Short Term headers), simply deleting it will wipe out those titles.
    
    To safely delete an anchor row:
    1. Multi-select columns D, E, and F of the row immediately below the anchor row.
    2. Copy them (Ctrl+C) and paste them (Ctrl+V) directly onto Cell D of the anchor row. Both rows will now share the same identity.
    3. Verify the Validation Level: Look at columns G and H (Debit/Credit Validation) and confirm that the selectable configuration for the Journal dropdown menus is preserved.
    4. You can now safely delete the original row below the anchor. Because the account data was moved to the anchor row in Step 2, your section titles in Columns A, B, and C are preserved.

Industry Alignment (Farming vs. Non-Farming)

Default templates include specialized sections for agricultural reporting.

If your business is not tied to agriculture, you should delete the rows belonging to the “Farming Revenue” and “Farming Expenses” sections. While the Abaque engine remains functional if they are removed, it is recommended to preserve summary row 9970 | 7970 | Net Income/Loss Before [Tx & ]Extraordinary Items from the “Farming Expenses” section. This row provides a valuable calculation of your net position before extraordinary items and income tax (for corporations). This summary row should be positioned directly below 9369 | 5969 | Net Non-Farming Income once the other “Farming” section rows are deleted. Here is how the bottom of the CoA Expenses section should look once the deletion operation is complete:

For businesses that do have agricultural operations, the GIFI standard allows for two different ways to organize your ledger:

• Option A: Comprehensive Separation. Keep all four sections (two Non-Farming and two Farming). This is ideal if you want to strictly segregate your agricultural activities or if you prefer the thorough, classification codes provided within the Non-Farming sections for your general business income and expenses.
• Option B: Simplified Integration. If your farming operations are straightforward, you can consolidate your reporting. The GIFI standard provides specific codes for this purpose, such as 9650 — Non-farming income for reporting general revenue within a farming section when GIFI codes 8000 to 8299 are not used, and 9850 — Non-farming expenses if you are not using items 8300 to 9368 for any non-farming expenses. In this scenario, the two general non-farming sections can be removed, resulting in a leaner, more efficient CoA.

Predefined Items

The following list enumerates the predefined items used by the Abaque engine. These items serve two primary functional roles:

1. Summary Accounts (Totals & Subtotals): Used for establishing system-calculated totals of sections and categories. Unless otherwise noted, these structural items are read-only and cannot be used as a DEBIT or CREDIT entry within the Journal.
2. Tax Anchors: Used for calculating sales tax account balances and mapping regional tax liabilities.