ERPNext Accounting in the Philippines

Books of accounts and a computerized system the BIR may review

Philippine companies that keep their books in software are generally expected to have that system registered with, or acknowledged by, the BIR, and to be able to produce books of accounts and supporting records on request. The exact requirements, forms and whether your situation calls for registration or a simpler acknowledgment are questions for your tax advisor, and they change from time to time. What I can do is make sure ERPNext produces what that advisor asks for.

ERPNext stores every posting in its general ledger and keeps a version history on documents, which gives a good starting point for an audit trail. The work lies in presentation and control:

• Books. The general journal and general ledger come from standard reports. Sales, purchase, cash receipts and disbursement books usually need query or script reports with the columns your advisor specifies.
• Corrections. Submitted documents are cancelled and amended rather than edited, so the original stays visible. I check that users cannot bypass this through permissions.
• Period locks. Accounting periods and a frozen-entries date stop late changes once a month is reported.
• System description. A plain inventory of modules, custom apps and report names, ready for your advisor to use.

For the module in general, see ERPNext Accounting.

Expanded withholding on supplier bills through withholding categories

ERPNext has a Tax Withholding Category record that was designed to be generic: you define a rate, an account and optional thresholds, attach the category to suppliers, and purchase invoices or payments deduct the tax automatically. For a Philippine company, that mechanism can carry expanded withholding on professional fees, rentals, contractors and other payments your advisor considers in scope.

The decisions I work through with finance are practical ones:

• One category per treatment. Separate categories for each type of payment your advisor distinguishes, so totals can be reported by type without manual sorting.
• Supplier data at onboarding. TIN, registered address and the default category entered when the supplier is created, with a mandatory field rule so the clerk cannot skip it.
• Bills or payments. Deducting on the purchase invoice suits most service suppliers; deducting on advance payments needs extra testing.
• Certificate data. A report listing tax withheld per supplier, per period and per category, giving whoever prepares certificates and summary lists a source that ties to the ledger.

Whether any Philippine-specific app or form layout exists for your ERPNext version is something I confirm with your implementer before deciding what to build. Unknowns go into the gap analysis with an owner and an estimate.

Tax withheld by your customers and receipts that arrive short

Corporate customers in the Philippines often deduct withholding before paying your invoice and are expected to send a certificate afterward. If the receipt is posted as a partial payment, the invoice stays open, receivables look overdue and the creditable tax disappears from view.

In ERPNext the cleaner route is the deductions table on the payment entry. The cashier records the amount received, then adds a deduction line that posts the withheld portion to a creditable withholding account, and the invoice closes in full. I set this up with:

• A dedicated asset account for creditable withholding, separate from input VAT and other prepaid taxes.
• A custom field on the payment entry for the certificate status, so collections staff can see which customers still owe a certificate for which period.
• A report of creditable amounts by customer and quarter, ready for your accountant to match against certificates received.
• Bank charges on overseas dollar receipts posted as a second deduction line, keeping fees apart from tax.

Service exporters and outsourcing firms feel this most, because local clients withhold while foreign clients pay gross. Related patterns are on finance automation.

Bank formats, e-wallets and peso and dollar books

ERPNext reconciles bank accounts by importing statements and matching them against payment entries and journal entries in the Bank Reconciliation Tool. Philippine banks each export statements in their own layout, and some business accounts offer only PDF statements, so I collect a sample from every bank you use and build an import template for each. Where only PDF is available, we agree a conversion step and who owns it.

E-wallet and card settlements need their own design. Collections through wallets or payment gateways usually arrive net of fees, in batches, sometimes days later. I treat each provider as a clearing account: sales post to the clearing account, the settlement report moves the net amount to the bank, and fees post as an expense. The clearing balance should fall to zero for each settlement period.

On currency, the Philippine company reports in pesos, yet a USD receivable account, a dollar bank account or a foreign supplier can sit alongside it. Outsourcing firms and exporters invoicing in USD need exchange revaluation at month end and a decision, with your accountant, on which rates to use. Groups with an overseas parent add intercompany charges, which ERPNext supports through internal customers and suppliers. The broader patterns are on multi-currency ERP.

E-invoicing, upgrades and who maintains the custom apps

The Philippines has been moving toward electronic invoicing and electronic sales reporting for certain taxpayers. ERPNext exposes a full API, so a connection can be built, but I would not assume a ready-made Philippine connector exists for your version. Confirm with Frappe or your implementer what is available, who maintains it and whether it is tested against the current specifications. Your advisor confirms whether and when the rules apply to you.

Every local report and integration you add becomes code that must survive upgrades. ERPNext is released under an open source license, so there is no license fee, but there is also no vendor obliged to keep your custom apps working. A sensible routine includes:

• All custom work in a separate app under version control, never edits to core files.
• A staging site where each upgrade is tested against your books and withholding reports before production moves.
• A written record of changes, so the system your advisor described stays consistent with what runs.
• A named owner for each app: your developer, an implementer or a Frappe Cloud support plan.

Frappe does not pay me, and no hosting or support contract earns me anything. The platform view is on my ERPNext consultant Philippines page, with wider context on the Philippines ERP consultant page and the Philippines hub. Delivery is remote, and the engagement runs in English.