EazLink guide
What should you ask a BIR EIS integration provider?
A buyer checklist for scope, data ownership, certification support, security, downtime, evidence and support boundaries.
Updated 2026-09-06 by the EazLink team. Editorial review: EazLink Editorial Team.
Direct answer
Ask a provider to explain the exact taxpayer and system scope, how invoice data enters the platform, where credentials are stored, what happens after a timeout, how corrections and duplicates work, what evidence remains available, and which certification tasks are included. Avoid claims of guaranteed approval. The BIR controls certification and permission.
What to remember
- Ask for a live exception workflow as well as a successful demo.
- Separate implementation, certification support and BIR decisions.
- Confirm data location, access and retention.
- Put ERP, provider and taxpayer responsibilities in writing.
Questions that expose delivery risk
A precise answer is more useful than a long feature list.
| Area | Ask | Good evidence |
|---|---|---|
| Scope | Which entities, branches and systems are included? | Written inventory and assumptions |
| Failure handling | What happens after timeout or rejection? | State model and runbook |
| Security | Who can access keys and taxpayer data? | Architecture and access controls |
| Certification | Which tasks are support versus official decision? | Clear responsibility matrix |
| Support | Who owns a bad source field? | Named escalation path |
Make the provider draw the data flow
The diagram should show source systems, integration points, authentication, data storage, logs and status return. It should also show where personal and taxpayer data crosses a boundary.
A box labelled cloud is not enough. Ask which team owns every connection and credential.
Test the uncomfortable scenarios
Request a demonstration of rejection, timeout, duplicate attempt and source-system correction. Ask how an operator finds and resolves each case.
Review what happens when the provider service, the BIR service or a branch network is unavailable. These are different failures.
Define the support boundary
EazLink separates the source adapter, shared compliance layer and official BIR process. Partners can own the customer and ERP work while EazLink owns the agreed middleware service.
The proposal should state what is outside scope, including tax opinions and guaranteed approval.
Provider evaluation
- Verify taxpayer and system scope.
- Review architecture and data controls.
- Run failure demonstrations.
- Read the certification responsibility matrix.
- Check support hours, escalation and exit data.
Quick questions
Should a vendor guarantee BIR certification?
No provider controls the BIR decision. Look for competent preparation, testing and evidence rather than a guarantee.
What is the most important demo?
A failed or timed-out transaction shows more about operating quality than a successful happy path.
Who should own source-data errors?
The business or source-system partner usually owns the correction. Middleware should identify the field and preserve the failed attempt.
Continue the preparation
Sources and verification
Check the current BIR rules and portal notices before making a compliance decision.