<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Boongon team</title>
    <description>The latest articles on DEV Community by Boongon team (@boongon).</description>
    <link>https://dev.to/boongon</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4213005%2F048d8ded-653c-4079-b97d-556f12e0e382.png</url>
      <title>DEV Community: Boongon team</title>
      <link>https://dev.to/boongon</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/boongon"/>
    <language>en</language>
    <item>
      <title>Multi-Currency, Multi-Entity Accounting: Consolidation Basics for Cross-Border and Export Businesses</title>
      <dc:creator>Boongon team</dc:creator>
      <pubDate>Mon, 16 Nov 2026 10:37:20 +0000</pubDate>
      <link>https://dev.to/boongon/multi-currency-multi-entity-accounting-consolidation-basics-for-cross-border-and-export-businesses-40ij</link>
      <guid>https://dev.to/boongon/multi-currency-multi-entity-accounting-consolidation-basics-for-cross-border-and-export-businesses-40ij</guid>
      <description>&lt;p&gt;&lt;em&gt;By the Boongon team&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The first time a business sets up a company in another country, it usually feels like an operational decision: a sales office in Dubai, a sourcing company in Vietnam, a US entity to sell to American customers, a Canadian subsidiary for a big contract. The accounting consequences arrive a few months later, when someone asks a simple question: "How much did the group make last quarter?"&lt;/p&gt;

&lt;p&gt;This guide covers the basics of running several companies in several currencies: the terms you need, the month-end steps, and what your systems should handle so consolidation isn't a two-week spreadsheet exercise.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three currencies you need to keep apart
&lt;/h2&gt;

&lt;p&gt;Most confusion comes from mixing these up.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Transaction currency:&lt;/strong&gt; the currency on the invoice. A Mexican subsidiary might bill a US customer in USD.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Functional currency:&lt;/strong&gt; the currency of the primary economic environment each entity operates in. Usually the local currency: MXN for the Mexican company, AED for the UAE company.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Presentation (reporting) currency:&lt;/strong&gt; the currency the group reports in. Often USD for groups selling into the Americas, but it can be anything.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each entity keeps its books in its functional currency. Transactions in other currencies are converted at the transaction date. Consolidation then translates each entity into the presentation currency.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Get the entity-level books right
&lt;/h2&gt;

&lt;p&gt;Consolidation can only be as good as the books underneath it. For each entity:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Record foreign-currency transactions at the rate on the transaction date.&lt;/strong&gt; Use a consistent, documented rate source.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Revalue open foreign-currency balances at month end.&lt;/strong&gt; Receivables, payables and bank accounts in a foreign currency are restated at the closing rate. The difference is an unrealised exchange gain or loss in profit and loss.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Book realised gains and losses on settlement.&lt;/strong&gt; When a USD invoice is paid at a different rate from the one it was booked at, the difference is realised.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reverse or roll forward unrealised revaluations consistently,&lt;/strong&gt; so you don't double-count when the item is settled.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If this is done in a spreadsheet and posted as a single journal, check it every month. It's the most common source of small, persistent errors.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Track intercompany transactions from day one
&lt;/h2&gt;

&lt;p&gt;Intercompany activity is anything between two companies in the same group: management fees, inventory sold from the sourcing company to the sales company, loans, recharged costs.&lt;/p&gt;

&lt;p&gt;The golden rule: &lt;strong&gt;both sides must be recorded, in the same period, for the same amount (in the transaction currency).&lt;/strong&gt; Then:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use dedicated intercompany receivable and payable accounts, per counterparty.&lt;/li&gt;
&lt;li&gt;Agree balances between entities before month-end close, not after.&lt;/li&gt;
&lt;li&gt;Settle regularly, so balances don't grow into large unreconciled numbers with large FX differences.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Many groups use intercompany "mirroring": when entity A raises an invoice to entity B, the matching bill is created in B automatically. This removes most timing differences.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Translate into the presentation currency
&lt;/h2&gt;

&lt;p&gt;Under both IFRS (IAS 21) and US GAAP (ASC 830), the standard approach for a subsidiary whose functional currency differs from the group's presentation currency is:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Item&lt;/th&gt;
&lt;th&gt;Rate used&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Assets and liabilities&lt;/td&gt;
&lt;td&gt;Closing rate at the balance sheet date&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Income and expenses&lt;/td&gt;
&lt;td&gt;Rate at transaction date, or an average rate for the period as a practical approximation&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Equity (share capital, opening retained earnings)&lt;/td&gt;
&lt;td&gt;Historical rates&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Resulting difference&lt;/td&gt;
&lt;td&gt;Other comprehensive income, accumulated in a currency translation reserve (CTA)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The translation difference is not a profit or loss of the period. It's the effect of exchange rates on the value of your investment in the subsidiary, and it sits in equity until the subsidiary is sold.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This is a simplified summary. Hyperinflationary economies, highly integrated foreign operations and specific local GAAP rules can change the treatment, so confirm your approach with your auditor.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Eliminate intercompany balances and transactions
&lt;/h2&gt;

&lt;p&gt;The group can't owe itself money or make a profit selling to itself. On consolidation you eliminate:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Intercompany receivables against intercompany payables&lt;/li&gt;
&lt;li&gt;Intercompany sales against intercompany purchases or cost of sales&lt;/li&gt;
&lt;li&gt;Intercompany management fees, interest and dividends&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unrealised profit in inventory:&lt;/strong&gt; if the sourcing company sold goods to the sales company at a markup and they're still in stock at period end, that markup must be removed from group inventory and group profit&lt;/li&gt;
&lt;li&gt;The parent's investment in each subsidiary against the subsidiary's share capital&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If the two sides of an intercompany balance don't agree after translation, the difference is usually an FX timing issue or a missing entry. Investigate it; don't plug it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: Handle ownership that isn't 100%
&lt;/h2&gt;

&lt;p&gt;If a subsidiary is partly owned, for example 70% with a local partner (common for joint ventures and in markets with foreign-ownership limits), the group still consolidates 100% of its assets, liabilities, income and expenses, then shows the 30% belonging to the partner as a &lt;strong&gt;non-controlling interest&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  A month-end consolidation checklist
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;#&lt;/th&gt;
&lt;th&gt;Task&lt;/th&gt;
&lt;th&gt;Owner&lt;/th&gt;
&lt;th&gt;Done&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Close each entity's sub-ledgers (sales, purchases, inventory, payroll)&lt;/td&gt;
&lt;td&gt;Entity accountant&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Load closing and average exchange rates from the agreed source&lt;/td&gt;
&lt;td&gt;Group finance&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Revalue foreign-currency balances in each entity&lt;/td&gt;
&lt;td&gt;Entity accountant&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;Agree intercompany balances with every counterparty&lt;/td&gt;
&lt;td&gt;Both entities&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;Resolve intercompany differences above the agreed threshold&lt;/td&gt;
&lt;td&gt;Group finance&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;Lock the period in each entity&lt;/td&gt;
&lt;td&gt;Entity accountant&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;Translate each entity into the presentation currency&lt;/td&gt;
&lt;td&gt;Group finance&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;Post eliminations, including unrealised profit in stock&lt;/td&gt;
&lt;td&gt;Group finance&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;Review the currency translation reserve movement&lt;/td&gt;
&lt;td&gt;Group controller&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;Produce group P&amp;amp;L, balance sheet and cash flow; tie out to entity totals&lt;/td&gt;
&lt;td&gt;Group controller&lt;/td&gt;
&lt;td&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  What your systems should do
&lt;/h2&gt;

&lt;p&gt;When a group has two or three entities, spreadsheets can cope. By the time there are four or more, or the entities trade with each other regularly, look for a system that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Keeps every entity in its own functional currency, in one database&lt;/li&gt;
&lt;li&gt;Revalues foreign-currency balances automatically, with the journals visible&lt;/li&gt;
&lt;li&gt;Mirrors intercompany invoices and bills between entities&lt;/li&gt;
&lt;li&gt;Translates and consolidates on demand, not only at month end&lt;/li&gt;
&lt;li&gt;Eliminates intercompany balances with an audit trail&lt;/li&gt;
&lt;li&gt;Lets you restrict users to one entity without separate logins&lt;/li&gt;
&lt;li&gt;Flags any entity missing an exchange rate instead of silently dropping it from the total&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last point sounds small. A consolidated report that quietly leaves out a subsidiary because a rate was missing is worse than no report at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where Boongon fits
&lt;/h2&gt;

&lt;p&gt;Boongon is a cloud ERP that keeps several companies in their own currencies on one ledger, with revaluation, intercompany mirroring, currency translation for reporting and a consolidated view that names any company missing a rate. Extra companies carry a monthly charge on the standard plans; consolidation, eliminations and per-entity access are part of the Enterprise plan. If your group is outgrowing the spreadsheet, you can test the entity-level side in a 14-day trial with no card, or ask for a working session on consolidation. Start at &lt;a href="https://boongon.com" rel="noopener noreferrer"&gt;boongon.com&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>accounting</category>
      <category>erp</category>
      <category>finance</category>
      <category>smallbusiness</category>
    </item>
    <item>
      <title>BIR Compliance Checklist for Growing Philippine SMEs: Monthly, Quarterly and Annual Forms</title>
      <dc:creator>Boongon team</dc:creator>
      <pubDate>Tue, 03 Nov 2026 10:11:06 +0000</pubDate>
      <link>https://dev.to/boongon/bir-compliance-checklist-for-growing-philippine-smes-monthly-quarterly-and-annual-forms-4chf</link>
      <guid>https://dev.to/boongon/bir-compliance-checklist-for-growing-philippine-smes-monthly-quarterly-and-annual-forms-4chf</guid>
      <description>&lt;p&gt;&lt;em&gt;By the Boongon team&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;When a Philippine business is small, BIR compliance usually lives with one bookkeeper, a folder of receipts and a spreadsheet. That works until you have more suppliers who withhold from you, more employees, a second branch, or a client who keeps asking for their 2307s. Then the deadlines start to collide.&lt;/p&gt;

&lt;p&gt;This guide lists the returns and attachments a typical VAT- or percentage-tax-registered corporation deals with, groups them by frequency, and explains what your accounting system should produce for each so that filing becomes a review, not a reconstruction.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Important:&lt;/strong&gt; BIR rules change. The TRAIN law moved VAT to quarterly filing, and the Ease of Paying Taxes (EOPT) Act changed invoicing and some filing rules. Always confirm current forms and due dates with your RDO, the BIR website or your accountant. This article is a planning aid, not tax advice.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Start with your registration: which taxes apply to you?
&lt;/h2&gt;

&lt;p&gt;Your Certificate of Registration (Form 2303) lists the tax types you must file. Check it before building any calendar. The common combinations are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;VAT-registered:&lt;/strong&gt; quarterly VAT (2550Q), plus withholding returns if you have employees or pay suppliers subject to expanded withholding tax (EWT).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Non-VAT (percentage tax):&lt;/strong&gt; quarterly percentage tax (2551Q) instead of VAT.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Withholding agent:&lt;/strong&gt; almost every business with employees or regular suppliers. This brings 1601-C, 0619-E / 1601-EQ and possibly 0619-F / 1601-FQ, plus the annual information returns.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If a tax type is on your COR and you have nothing to report, you generally still file a "no operations" return. Missed zero returns are one of the most common sources of penalties for growing SMEs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Monthly obligations
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Form&lt;/th&gt;
&lt;th&gt;What it is&lt;/th&gt;
&lt;th&gt;Typical due date&lt;/th&gt;
&lt;th&gt;What your system should produce&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;1601-C&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Monthly remittance of tax withheld on compensation&lt;/td&gt;
&lt;td&gt;10th of the following month (eFPS filers are staggered; December is due 15 January)&lt;/td&gt;
&lt;td&gt;Withholding totals per employee straight from payroll, reconciled to the payroll journal&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;0619-E&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Monthly remittance of expanded withholding tax (first two months of the quarter)&lt;/td&gt;
&lt;td&gt;10th of the following month&lt;/td&gt;
&lt;td&gt;EWT withheld on supplier payments, by ATC code, tied to the bills it came from&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;0619-F&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Monthly remittance of final withholding tax (first two months of the quarter)&lt;/td&gt;
&lt;td&gt;10th of the following month&lt;/td&gt;
&lt;td&gt;Final tax withheld (e.g. on certain rentals, dividends, interest to non-residents)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;2550M&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Monthly VAT declaration&lt;/td&gt;
&lt;td&gt;Optional since 2023 for most taxpayers; confirm with your RDO&lt;/td&gt;
&lt;td&gt;Output and input VAT by month, even if you only file quarterly, so your quarter has no surprises&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Quarterly obligations
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Form&lt;/th&gt;
&lt;th&gt;What it is&lt;/th&gt;
&lt;th&gt;Typical due date&lt;/th&gt;
&lt;th&gt;What your system should produce&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;2550Q&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Quarterly VAT return&lt;/td&gt;
&lt;td&gt;25th day after the quarter ends&lt;/td&gt;
&lt;td&gt;Output VAT from sales invoices, input VAT from purchases, with the SLSP that supports them&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;2551Q&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Quarterly percentage tax (non-VAT)&lt;/td&gt;
&lt;td&gt;25th day after the quarter ends&lt;/td&gt;
&lt;td&gt;Gross sales by quarter, at the correct rate&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;1601-EQ&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Quarterly EWT return&lt;/td&gt;
&lt;td&gt;Last day of the month after the quarter ends&lt;/td&gt;
&lt;td&gt;Quarter totals by ATC, with the QAP (Quarterly Alphalist of Payees)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;1601-FQ&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Quarterly final withholding return&lt;/td&gt;
&lt;td&gt;Last day of the month after the quarter ends&lt;/td&gt;
&lt;td&gt;Quarter totals plus the payee alphalist&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;2307&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Certificate of creditable tax withheld, issued to each supplier you withheld from&lt;/td&gt;
&lt;td&gt;Within 20 days after the quarter ends (or on request)&lt;/td&gt;
&lt;td&gt;One certificate per payee per quarter, generated from the same bills used for 1601-EQ&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;SLSP&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Summary List of Sales and Purchases&lt;/td&gt;
&lt;td&gt;With the quarterly VAT return&lt;/td&gt;
&lt;td&gt;Sales and purchases by customer and supplier TIN&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;SAWT&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Summary Alphalist of Withholding Taxes&lt;/td&gt;
&lt;td&gt;Attached to returns where you claim credits&lt;/td&gt;
&lt;td&gt;Every 2307 you &lt;em&gt;received&lt;/em&gt; from customers, matched to the invoice it relates to&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;1702Q&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Quarterly income tax return (corporations)&lt;/td&gt;
&lt;td&gt;60 days after the quarter ends&lt;/td&gt;
&lt;td&gt;Year-to-date profit and loss with tax adjustments&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The quarterly cycle is where most of the work concentrates. The VAT return, the EWT return, the 2307s you issue and the 2307s you collect all land within roughly five weeks of each other.&lt;/p&gt;

&lt;h2&gt;
  
  
  Annual obligations
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Form&lt;/th&gt;
&lt;th&gt;What it is&lt;/th&gt;
&lt;th&gt;Typical due date&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;1604-C&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Annual information return of income taxes withheld on compensation&lt;/td&gt;
&lt;td&gt;31 January&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;2316&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Certificate of compensation and tax withheld, given to each employee&lt;/td&gt;
&lt;td&gt;Issued by 31 January; copies submitted to the BIR by 28 February&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;1604-E&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Annual information return of creditable (expanded) withholding taxes&lt;/td&gt;
&lt;td&gt;1 March&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;1604-F&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Annual information return of final withholding taxes&lt;/td&gt;
&lt;td&gt;31 January&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;2306&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Certificate of final tax withheld, issued to payees&lt;/td&gt;
&lt;td&gt;With or after the relevant payment, as required&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;1702-RT / 1702-EX / 1702-MX&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Annual corporate income tax return&lt;/td&gt;
&lt;td&gt;15th day of the fourth month after year end (15 April for calendar years)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Books of Accounts&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Registered journals and ledgers (manual, loose-leaf or computerised)&lt;/td&gt;
&lt;td&gt;Kept throughout the year; loose-leaf and computerised books have year-end submission requirements&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  The documents that cause the most trouble
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;2307s you receive.&lt;/strong&gt; If a customer withholds 1% or 2% from your payment, that withholding only becomes a tax credit when you hold the 2307 and list it in your SAWT. Growing businesses routinely lose credits because nobody chases the certificates. Track each one against the invoice it relates to and the quarter it belongs to.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2307s you issue.&lt;/strong&gt; Suppliers will ask for them, and late certificates damage relationships. If your EWT is recorded on the bill when you pay it, the 2307 should be a printout, not a project.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;ATC codes.&lt;/strong&gt; Each EWT line needs the right alphanumeric tax code (for example professional fees versus rentals versus goods). Set the code on the supplier or the expense account so it does not depend on the person encoding the bill.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;TINs and branch codes.&lt;/strong&gt; SLSP, QAP and SAWT are lists keyed by TIN. A missing or wrong TIN on a supplier record will follow you into every attachment.&lt;/p&gt;

&lt;h2&gt;
  
  
  What your accounting system should do for you
&lt;/h2&gt;

&lt;p&gt;Use this as a checklist when you review your current setup, or when you evaluate a new one.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Withholding is calculated on the bill or payment, not added afterwards in a spreadsheet&lt;/li&gt;
&lt;li&gt;[ ] Every supplier and customer record carries a TIN, branch code and default ATC&lt;/li&gt;
&lt;li&gt;[ ] 2307s can be generated per payee per quarter from posted transactions&lt;/li&gt;
&lt;li&gt;[ ] 2307s received can be recorded against specific invoices and feed the SAWT&lt;/li&gt;
&lt;li&gt;[ ] SLSP, QAP and SAWT export in the format the BIR expects&lt;/li&gt;
&lt;li&gt;[ ] VAT is tracked monthly even though you file quarterly&lt;/li&gt;
&lt;li&gt;[ ] Payroll withholding flows to 1601-C, 1604-C and the 2316s without re-keying&lt;/li&gt;
&lt;li&gt;[ ] Books of Accounts can be printed or exported in the layout your registration requires&lt;/li&gt;
&lt;li&gt;[ ] Every figure on a return can be traced back to the documents behind it&lt;/li&gt;
&lt;li&gt;[ ] You can tell, today, which returns are due in the next 30 days&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you tick fewer than half of these, the risk isn't just penalties. It's the time your team spends rebuilding the same numbers every month.&lt;/p&gt;

&lt;h2&gt;
  
  
  A simple monthly routine
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;By the 5th:&lt;/strong&gt; close the previous month's sales and purchases; chase missing supplier invoices.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;By the 8th:&lt;/strong&gt; review EWT and compensation withholding; prepare 1601-C and 0619-E/F.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;By the 10th:&lt;/strong&gt; file and pay.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;In the first three weeks after quarter end:&lt;/strong&gt; issue 2307s, collect the 2307s owed to you, reconcile VAT, prepare SLSP.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;By the 25th after quarter end:&lt;/strong&gt; file 2550Q or 2551Q.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;By month end after quarter end:&lt;/strong&gt; file 1601-EQ/FQ with the alphalists.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Where Boongon fits
&lt;/h2&gt;

&lt;p&gt;Boongon is a cloud ERP with a Philippine tax layer built in. It prepares the 2550M/Q, 2551Q, 1601-C, 1601-EQ, 1601-FQ, the 1604 series, 2307, 2306, 2316, SLSP, SAWT and the Books of Accounts from the same ledger your transactions post to. It doesn't e-file (you still file through eBIRForms or eFPS), the 0619 forms and the QAP are only partly prepared, and the 1702 income tax returns aren't built yet. If you want to see whether it would take the quarter-end scramble off your team, the 14-day trial needs no card, and it's for teams of five users or more. Start at &lt;a href="https://boongon.com" rel="noopener noreferrer"&gt;boongon.com&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>bir</category>
      <category>philippines</category>
      <category>accounting</category>
      <category>tax</category>
    </item>
    <item>
      <title>Designing enforced approval workflows on a single ledger</title>
      <dc:creator>Boongon team</dc:creator>
      <pubDate>Wed, 28 Oct 2026 12:00:45 +0000</pubDate>
      <link>https://dev.to/boongon/designing-enforced-approval-workflows-on-a-single-ledger-4enm</link>
      <guid>https://dev.to/boongon/designing-enforced-approval-workflows-on-a-single-ledger-4enm</guid>
      <description>&lt;p&gt;&lt;em&gt;By the Boongon team&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Most business apps implement approvals in the UI. The "Post" button is disabled until the document is approved, and that's that. It works until the day someone posts the same document through an import, an API call, a background job or a new screen that forgot the check.&lt;/p&gt;

&lt;p&gt;In accounting software that's a control failure, not a cosmetic bug. Here are the design principles we think matter when approvals must be &lt;em&gt;enforced&lt;/em&gt;, not just displayed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Principle 1: A hidden button is not a control
&lt;/h2&gt;

&lt;p&gt;If the rule lives in a front-end component, it only binds people who use that component. The rule needs to sit at the narrowest point every write passes through: as close to the data as you can get.&lt;/p&gt;

&lt;p&gt;In practice that means the "can this document be posted?" check runs in the same transaction that changes the document's status, and it runs no matter which code path initiated the change. A useful mental test:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;If a new developer adds a new endpoint next year and forgets about approvals entirely, does the rule still hold?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;If the answer is "no", the control lives in the wrong layer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Principle 2: Model the approval as state on the document
&lt;/h2&gt;

&lt;p&gt;Treat approval as part of the document's lifecycle, not a side table someone might consult:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;draft -&amp;gt; submitted -&amp;gt; under_approval -&amp;gt; approved -&amp;gt; posted
                          |
                          v
                       rejected -&amp;gt; draft
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two invariants do most of the work:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A document can only move to &lt;code&gt;posted&lt;/code&gt; from &lt;code&gt;approved&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;A document that is &lt;code&gt;under_approval&lt;/code&gt; or later cannot have its financial fields changed.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The second one is easy to miss. If the amount can be edited after the last sign-off, the approval refers to a document that no longer exists. Locking the fields once approval starts means "who approved what" stays meaningful.&lt;/p&gt;

&lt;h2&gt;
  
  
  Principle 3: Rules are data, matched at submission
&lt;/h2&gt;

&lt;p&gt;Approval rules usually look like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;document_type = purchase_invoice
AND amount &amp;gt; threshold
AND cost_centre = X
=&amp;gt; steps: [site_manager, commercial, finance_director]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Store rules as data, and when a document is submitted, resolve which rule applies and snapshot the resulting steps onto that document. Snapshotting matters: if someone changes the rule tomorrow, documents already in flight should finish under the rule they started with, and your history should show which rule version applied.&lt;/p&gt;

&lt;p&gt;Assign steps to &lt;strong&gt;roles&lt;/strong&gt;, not people.&lt;/p&gt;

&lt;h2&gt;
  
  
  Principle 4: One ledger, so there's only one door
&lt;/h2&gt;

&lt;p&gt;Approvals get much harder when the business event and its accounting consequence live in different systems. If the purchase invoice lives in one app and the journal in another, you need the approval rule in both, or a sync that can't race.&lt;/p&gt;

&lt;p&gt;A single ledger, where posting the invoice &lt;em&gt;is&lt;/em&gt; creating its journal in the same transaction, means there's one door to guard. It also gives you traceability for free: a profit and loss line opens to the journal, which opens to the invoice, which opens to its approval steps.&lt;/p&gt;

&lt;h2&gt;
  
  
  Principle 5: Never edit posted data, reverse it
&lt;/h2&gt;

&lt;p&gt;Once something is posted, updates should be refused. Corrections are new, linked entries that reverse the original, and both stay visible. This keeps the approved record intact and makes the correction itself subject to the same rules.&lt;/p&gt;

&lt;h2&gt;
  
  
  Principle 6: Make the history tamper-evident
&lt;/h2&gt;

&lt;p&gt;An audit log in an ordinary table can be edited by anyone with enough privileges. A simple improvement is to chain entries: each row stores a hash of its own content plus the hash of the previous row.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;row_hash = H(actor, action, record_id, timestamp, payload, prev_row_hash)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Altering or deleting a row breaks every hash after it, and a periodic verification job can report "chain intact" or point to where the break is. It won't stop someone rewriting the whole chain, but it makes silent edits detectable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Principle 7: Automation is just another caller
&lt;/h2&gt;

&lt;p&gt;Imports, integrations, scheduled jobs and now AI assistants are all just callers. They should hit exactly the same enforcement as a person clicking a button. A clean pattern for AI in particular:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It can &lt;strong&gt;read&lt;/strong&gt; only what the requesting user is permitted to read.&lt;/li&gt;
&lt;li&gt;It can &lt;strong&gt;draft&lt;/strong&gt; documents, which enter the normal lifecycle as &lt;code&gt;draft&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;It can &lt;strong&gt;never post&lt;/strong&gt;. Drafts go through the same approval rules as anything a human raised.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If your enforcement lives at the data layer, you get this almost for free. If it lives in the UI, every new automation is a new hole.&lt;/p&gt;

&lt;h2&gt;
  
  
  Testing it
&lt;/h2&gt;

&lt;p&gt;The test suite that gives us the most confidence isn't a UI test. It's a set of tests that try to post an unapproved document through &lt;em&gt;every&lt;/em&gt; write path you have (each endpoint, the importer, each job) and assert that every one is refused with the same error. When a new path is added, it goes into that list.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wrapping up
&lt;/h2&gt;

&lt;p&gt;Enforced approvals come down to a few decisions: enforce at the data, lock what was approved, snapshot the rule, keep one ledger, reverse instead of edit, chain the history, and treat every automation as an ordinary caller.&lt;/p&gt;

&lt;p&gt;We build &lt;a href="https://boongon.com" rel="noopener noreferrer"&gt;Boongon&lt;/a&gt;, a cloud ERP where approvals are enforced where the data lives, on one ledger. We'd be interested to hear how others handle approval enforcement, especially across imports and integrations, in the comments.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The Boongon team&lt;/em&gt;&lt;/p&gt;

</description>
      <category>database</category>
      <category>architecture</category>
      <category>fintech</category>
      <category>backend</category>
    </item>
  </channel>
</rss>
