Xero/QBO + Philippine Tax Compliance Platform
Budget / Salary$5,000–10,000
TypeFreelance project
LocationRemote
Posted1 hour ago
We are looking for a company or developer that already has a substantially developed tax-compliance platform with working Xero and/or QuickBooks Online integration.
This project has two fundamental requirements:
1. You already have the platform
We are not looking to build the underlying platform from scratch.
Your existing platform should already have infrastructure for:
- Xero and/or QuickBooks Online integration
- Accounting-data ingestion and normalization
- Tax calculations and rules
- Compliance outputs
- Tax-form generation
- Working papers/supporting outputs
- Client/tenant management
- Audit trail and traceability
Please be prepared to demonstrate the existing platform and its working Xero/QBO integration.
2. Your platform can implement Philippine tax
The platform does not need to support Philippine tax today.
We will provide the Philippine tax-domain requirements, including tax classifications, calculation logic, rates, thresholds, effective dates, forms, mappings, test scenarios, and authoritative requirements.
Your role is to implement these requirements within your existing platform.
Scope clarification: Our actual requirement is Philippine tax compliance only. We are not asking you to build, prove, or price support for multiple jurisdictions. We ask about configurable tax architecture only to determine whether Philippine tax rules can be implemented within your existing platform without rebuilding the underlying system.
Required Output
The system must be capable of processing accounting data through the tax calculation and automatically populating the applicable official Philippine tax forms.
We are not looking for a system that merely produces calculated figures or reports that users must manually transfer onto the official forms.
BIR electronic transmission/e-filing is not required at this stage. The requirement is automated preparation and population of the official forms for human review and submission.
What We Need From You
Please provide:
1. A live demonstration of your existing platform and working Xero/QBO integration.
2. A demonstration showing accounting data → tax calculation → populated official tax form.
3. An explanation of how Philippine tax rules can be implemented within your existing tax engine.
4. Your source-code/IP ownership or licensing terms, including any restrictions on customization and commercial deployment.
5. Your estimated cost and implementation timeline, based on your assessment of the actual work required.
Screening Question
Taxpayer registration status — VAT-registered vs. non-VAT — comes from the taxpayer's BIR Certificate of Registration (Form 2303). This is user-supplied taxpayer-level data, not something derived automatically from Xero/QBO transactions.
The tax treatment should remain based on the registered status until the taxpayer's registration information is formally updated. A taxpayer should not be automatically reclassified simply because accounting data crosses a VAT registration threshold.
Please answer questions 1 and 2 directly and specifically. A general statement that your platform is "fully configurable" or "flexible" without addressing these two points directly will not be treated as a complete response.
1. How would your platform model a taxpayer-level status field that drives two separate calculation paths (VAT vs. percentage tax)? Please confirm that the tax engine does not automatically reclassify the taxpayer based solely on transaction data.
2. Can your platform identify and flag when a non-VAT taxpayer's revenue approaches or crosses the applicable registration threshold while their registered status remains non-VAT? This should be an advisory exception for human review, not an automatic change to the taxpayer's tax treatment.
We are looking for how your existing architecture represents and handles this scenario, not confirmation that your developers could code it.
Important
We are looking to reuse and adapt existing technology, not commission an entirely new platform.
You provide the existing technology platform. We provide the Philippine tax domain and rules.
This project has two fundamental requirements:
1. You already have the platform
We are not looking to build the underlying platform from scratch.
Your existing platform should already have infrastructure for:
- Xero and/or QuickBooks Online integration
- Accounting-data ingestion and normalization
- Tax calculations and rules
- Compliance outputs
- Tax-form generation
- Working papers/supporting outputs
- Client/tenant management
- Audit trail and traceability
Please be prepared to demonstrate the existing platform and its working Xero/QBO integration.
2. Your platform can implement Philippine tax
The platform does not need to support Philippine tax today.
We will provide the Philippine tax-domain requirements, including tax classifications, calculation logic, rates, thresholds, effective dates, forms, mappings, test scenarios, and authoritative requirements.
Your role is to implement these requirements within your existing platform.
Scope clarification: Our actual requirement is Philippine tax compliance only. We are not asking you to build, prove, or price support for multiple jurisdictions. We ask about configurable tax architecture only to determine whether Philippine tax rules can be implemented within your existing platform without rebuilding the underlying system.
Required Output
The system must be capable of processing accounting data through the tax calculation and automatically populating the applicable official Philippine tax forms.
We are not looking for a system that merely produces calculated figures or reports that users must manually transfer onto the official forms.
BIR electronic transmission/e-filing is not required at this stage. The requirement is automated preparation and population of the official forms for human review and submission.
What We Need From You
Please provide:
1. A live demonstration of your existing platform and working Xero/QBO integration.
2. A demonstration showing accounting data → tax calculation → populated official tax form.
3. An explanation of how Philippine tax rules can be implemented within your existing tax engine.
4. Your source-code/IP ownership or licensing terms, including any restrictions on customization and commercial deployment.
5. Your estimated cost and implementation timeline, based on your assessment of the actual work required.
Screening Question
Taxpayer registration status — VAT-registered vs. non-VAT — comes from the taxpayer's BIR Certificate of Registration (Form 2303). This is user-supplied taxpayer-level data, not something derived automatically from Xero/QBO transactions.
The tax treatment should remain based on the registered status until the taxpayer's registration information is formally updated. A taxpayer should not be automatically reclassified simply because accounting data crosses a VAT registration threshold.
Please answer questions 1 and 2 directly and specifically. A general statement that your platform is "fully configurable" or "flexible" without addressing these two points directly will not be treated as a complete response.
1. How would your platform model a taxpayer-level status field that drives two separate calculation paths (VAT vs. percentage tax)? Please confirm that the tax engine does not automatically reclassify the taxpayer based solely on transaction data.
2. Can your platform identify and flag when a non-VAT taxpayer's revenue approaches or crosses the applicable registration threshold while their registered status remains non-VAT? This should be an advisory exception for human review, not an automatic change to the taxpayer's tax treatment.
We are looking for how your existing architecture represents and handles this scenario, not confirmation that your developers could code it.
Important
We are looking to reuse and adapt existing technology, not commission an entirely new platform.
You provide the existing technology platform. We provide the Philippine tax domain and rules.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.