BIR Online Tools for IT and Software Consulting Firms: Managing Client Billing, BIR Form 2307, and SAWT

An IT or software consulting firm — whether a small dev shop or a larger outsourcing outfit — sits on both sides of creditable withholding tax at once. It is a withholding agent that must issue BIR Form 2307 to the freelance developers and subcontractors it pays for client project work, and it is also a payee that receives BIR Form 2307 certificates from the corporate clients withholding on the fees those clients pay the firm. BIR Online Tools handles both directions from one company profile.

This guide is for an IT or software consulting firm managing both its outgoing BIR Form 2307 certificates to developers and subcontractors and its incoming certificates from clients. For the withholding rate that applies when a business pays an individual developer directly versus a registered software company, see BIR Form 2307 for Software Developers and IT Consultants.

Why an IT consulting firm is a withholding agent too, not only a payee #

An IT consulting firm is easy to picture only as the party being withheld on — the one whose client sends a BIR Form 2307 — but that firm is also an ordinary business making payments of its own, and the BIR’s withholding-agent test doesn’t care that the payor happens to be a software shop. Revenue Regulations (RR) No. 2-98 defines who must withhold in terms broad enough to catch both a corporate client paying the firm and the firm itself paying its own freelance developers:

“(A) In general, any juridical person, whether or not engaged in trade or business; (B) An individual, with respect to payments made in connection with his trade or business…”

— RR No. 2-98, Section 2.57.3(A)–(B)

A firm organized as a corporation or partnership falls under clause (A) as a juridical person; a solo consultant running their own practice falls under clause (B) as an individual making payments in connection with their trade or business. Either way, the moment that firm pays a developer or subcontractor for work connected to a client engagement, it is the withholding agent for that payment — not the payee.

Individual freelance developer or subcontractor company — why the payee type changes the rate #

The withholding rate and ATC code the firm applies to its own developers turn on whether the payee is an individual providing personal technical services, or a company delivering the work as a business — not on the nature of the project itself.

An IT consulting firm engaging “Miguel Santos” directly as an individual freelance developer withholds under WI010/WI011 as a management/technical consultant. The same firm paying an invoice from a registered subcontractor corporation for an identical scope of work withholds under WC160 at the flat 2% contractor rate instead, because the payee is a business entity rather than an individually engaged consultant. BIR Form 2307 for Software Developers and IT Consultants covers the sworn-declaration mechanism that gets an individual developer the lower 5% rate.

What happens to the BIR Form 2307 certificates a firm receives from clients? #

Certificates an IT consulting firm receives from corporate clients withholding on its billed project fees are proof of creditable withholding tax (CWT) already deducted — proof the firm needs to consolidate into its own SAWT before it can claim that tax as a credit. When the firm itself is organized as a corporation delivering software development or IT consulting services as a business, a client paying it generally withholds under the same flat 2% contractor rate (ATC WC160) that applies to any corporate service provider, as described above.

Whatever rate the client applied, the firm’s job on the receiving end is the same: hold every certificate, match its totals to project invoices, and carry it into the Summary Alphalist of Withholding Tax (SAWT) that supports the CWT credit line on the firm’s own return. What Is SAWT? covers why the payee files this consolidated DAT listing rather than the withholding agent, and how a received certificate’s income and tax-withheld figures should reproduce exactly in the SAWT row built from it.

A worked quarterly scenario: issuing and receiving certificates in the same period #

A dev shop will typically be issuing BIR Form 2307 certificates to its freelance developers and reconciling certificates it received from clients in the same filing period — and the tool should keep those two flows separate without separate logins. Consider a fictional example: Nimbus Dev Studio, a software consulting firm organized as a corporation, in one calendar quarter.

Certificates received (client project fees):

Nimbus consolidates these two certificates into its SAWT DAT file for the quarter, carrying forward ₱32,000.00 in total tax withheld as the CWT credit it will apply against its income tax due.

Certificates issued (developer payments):

Nimbus issues each of the three freelance developers its own BIR Form 2307 at the applicable individual rate, remits the ₱26,500.00 withheld through the regular monthly and quarterly EWT returns, and keeps all three certificates in its DAT Repository alongside the two it received — one company profile, two directions of paperwork, neither mixed into the other.

Using BIR Online Tools for both directions #

BIR Online Tools keeps a single company profile for the firm while separating the module used to issue certificates to developers from the module used to build SAWT from certificates received. The BIR Form 2307 generator carries the firm’s own saved payor details — registered name, TIN, RDO code — into every certificate it issues to a developer like Ana Reyes or Lara Tan, without re-typing those details each time. Separately, the SAWT module is where the firm enters the certificates it received from Harborview Retail Group and Coastline Logistics, building the Alphalist DAT file that reconciles those two certificates against its own income tax return. For the broader walkthrough of setting up a company profile and moving between modules, see App Guide.

Frequently asked questions #

Is an IT or software consulting firm a withholding agent on payments it makes to its own freelance developers? #

Yes. Under RR No. 2-98, Section 2.57.3(A)-(B), any juridical person engaged in trade or business, and any individual with respect to payments made in connection with a trade or business, is required to withhold. An IT or software consulting firm organized as a corporation, partnership, or sole proprietorship falls within that definition the moment it pays a freelance developer, designer, or subcontractor for work connected to a client project.

Does it matter whether a developer is paid as an individual or through a subcontractor company? #

Yes. An individual freelance developer is generally withheld as a management/technical consultant under the 5%/10% individual professional-fee bracket (ATC WI010/WI011), while a software development or IT outsourcing company organized as a corporation is withheld under the flat 2% contractor rate (ATC WC160) instead — the deliverable can be identical, but the payee’s legal form changes which rate and ATC code applies.

What does an IT or software consulting firm do with the BIR Form 2307 certificates its corporate clients send it? #

The firm holds onto every certificate received as proof of creditable withholding tax (CWT) already deducted from its billed project fees, then consolidates those certificates into its own SAWT (Summary Alphalist of Withholding Tax) to support the CWT credit it claims on its income tax or VAT return, as covered in What Is SAWT.

Can BIR Online Tools track certificates issued to developers and certificates received from clients in the same account? #

Yes. A company profile in BIR Online Tools keeps a firm’s own payor details for generating BIR Form 2307 certificates to its freelance developers and subcontractors, while the SAWT module is where the firm enters the certificates it received from clients to build the SAWT DAT file for its own return — both live under the same firm profile without mixing the two directions together.

Does using BIR Online Tools’ SAWT module replace checking that the CWT a client withheld matches what was actually billed? #

No. The SAWT module converts entered certificate data into the Alphalist DAT layout the BIR expects; it doesn’t independently verify that a client applied the correct rate or amount. The firm still has to check each received BIR Form 2307 against its own project invoices before entering it, the same reconciliation step covered in SAWT Reconciliation with BIR Form 2307.

Summary #

An IT or software consulting firm’s creditable withholding tax workflow runs in two directions at once: it withholds and issues BIR Form 2307 to its own freelance developers and subcontractors under the general payor rule in RR No. 2-98, Section 2.57.3(A)-(B), applying WI010/WI011 to individual developers and WC160 to corporate subcontractors; and it receives BIR Form 2307 certificates from corporate clients that it must consolidate into its own SAWT to claim CWT credit. BIR Online Tools keeps both flows under one company profile — the BIR Form 2307 generator for issuing to developers, and the SAWT module for reconciling what the firm received. For the payee-side rate rules this post draws on, see BIR Form 2307 for Software Developers and IT Consultants; for the full app walkthrough, start at App Guide.