PRODUCT CAPABILITIES
What’s in scope.
01
Sales transaction integration
Connect the sales records supported by the implementation to the submission workflow. The published scope includes invoices, credit notes and POS entries rather than a separate manual recapture process.
02
API-based connection
Use the configured API and third-party service-provider integration to connect the ERP process with ZIMRA. The service relationship and required credentials are part of the deployment scope.
03
Submission traceability
Maintain visibility of the transactions submitted through the connector. Traceable records support investigation and review when the finance team needs to follow a transaction through the integration.
04
Deployment and validation
The published offer covers installation, configuration, user acceptance testing and go-live support. Cloud or on-premises suitability needs to be confirmed for the specific Business Central and LS Central environment.
Validate the transaction flow before go-live
The connector supports a tax-reporting process; the organisation remains responsible for confirming its requirements and reviewing the records submitted. Braintree can scope the environment, provider connection and testing around the supported transaction types.
✓
Confirm the Business Central or LS Central environment.
✓
Establish the service-provider connection and required access.
✓
Test invoices, credit notes and relevant POS scenarios.
✓
Agree responsibility for submission review, exceptions and support.
01
Connect the sales records already in your system
The ZIMRA VAT Connector described by Braintree connects supported Microsoft Dynamics 365 Business Central and LS Central sales transactions with the Zimbabwe Revenue Authority integration workflow. The published scope identifies sales invoices, credit notes and point-of-sale entries. That is the transaction boundary for the initial assessment: the team should establish which of those records the business produces and where they originate.
Braintree’s product information describes an API connection and integration with a third-party service provider. The provider relationship, account access and supported transaction flow therefore belong in the implementation scope. A connector between systems does not remove the need to review the records in the ERP or the responses received through the integration.
02
Follow each document through the connection
A useful review begins with a normal sales invoice and follows the information from the originating Business Central or LS Central record into the configured submission process. The same exercise should be completed for credit notes and relevant POS entries. Each document type can have different operational responsibilities, particularly when retail transactions and back-office invoicing are handled by different teams.
The published product offers submission traceability. Acceptance should establish what evidence is visible for the actual provider and version: the source document, the submission record and the information needed to investigate an exception. This is a scope for validation; it is not a claim that a particular response field, retry mechanism or fiscal-device feature has been verified by the available product material.
03
Confirm the ERP, retail and provider combination
The product page includes cloud and on-premises installation options. The assessment should identify the exact Business Central environment and whether LS Central participates in the sales process. Existing customisations, document layouts and other extensions may affect the integration points that need to be reviewed.
For a retail implementation, include the relationship between the POS transaction and the central accounting record. For back-office invoicing, identify the company and documents that will be submitted. Braintree can use this information to confirm compatibility and define the provider configuration work. Eligibility, credentials and any provider-side onboarding need confirmation for the organisation’s own arrangement.
04
Use testing to define readiness
The published engagement covers installation, configuration, user acceptance testing and go-live support. Those activities should be tied to a specific transaction set and acceptance record. Finance, retail operations where applicable, the ERP administrator and the integration provider need an agreed division of responsibility for the flow.
Record the companies, Business Central deployment and relevant LS Central environment.
Identify invoices, credit notes and POS scenarios that must be demonstrated.
Confirm the third-party service relationship and the access required for configuration.
Check how submission evidence is reviewed and how exceptions are escalated.
Agree the support scope and the conditions for moving the validated connection into operational use.
05
Keep transaction integration and tax responsibility clear
The connector provides a supported way to move transaction information and retain evidence for review. The organisation remains responsible for confirming the requirements applicable to its activities and the correctness of the underlying records. This page does not establish certification, universal coverage or an assurance that every transaction will be accepted.
After go-live, the operating procedure should identify who checks submission activity and who investigates a discrepancy between the sales record and the integration evidence. Any promised support allowance or service level must come from the agreed service terms. The purpose of the review is to confirm a usable process around the connector, not merely to show that two systems can exchange a sample record.
EVIDENCE & DOCUMENTATION
See the work in context.
BEFORE YOU DECIDE


