GST integration pilot readiness checklist
1. Define the source
- Name the system that produces the source data.
- Choose one source format for the pilot: JSON, CSV, XML, or a documented API response.
- Provide one invented, synthetic, or fully redacted fixture.
- Identify which source fields are always present and which are optional.
- State the approximate monthly document volume.
2. Define the expected output
- Name the exact output format or downstream interface.
- Provide an expected output for the synthetic fixture, if available.
- Specify required identifiers, dates, currency, and tax fields.
- State whether output field ordering or formatting is significant.
- List any downstream size, timeout, or compatibility constraints.
3. Agree transformation rules
- Document rounding precision and rounding mode.
- Define discount, freight, and other-charge treatment.
- Define mixed-rate, zero-rated, exempt, and reverse-charge behavior where relevant.
- Identify required totals and reconciliation equations.
- List validation failures that must stop transformation.
4. Make acceptance testable
- Agree the exact fixture used for acceptance.
- Agree expected output values for that fixture.
- Define the required automated tests and reproducible run command.
- Name the delivery format: repository, patch, or source archive.
- Define the allowed revision count and what counts as an in-scope correction.
5. Confirm commercial boundaries
- Agree a fixed price, currency, payment method, and payment timing in writing.
- Agree a delivery date or duration.
- Separate the pilot from production deployment, hosting, monitoring, and ongoing support.
- Identify additional formats, jurisdictions, workflows, and edge cases as out of scope unless written into the proposal.
- Confirm that work starts only after scope, acceptance criteria, price, and payment timing are agreed.
Safety boundary
Do not submit credentials, API keys, production invoices, personal records, taxpayer secrets, or live customer data. The pilot is a technical mapping and validation engagement; it does not constitute official IRP submission, certification, legal advice, or tax advice.
Build a draft acceptance pack
Turn the checklist into a structured JSON draft containing the fixture, mapping rules, acceptance evidence, delivery boundaries, and terms still to be agreed. The builder runs only in your browser and does not submit or store its fields.
Ready for a scoped discussion?
Submit non-confidential project metadata. A clarification reply may follow before any proposal is prepared. Submitting the form does not create an order or payment obligation.