PRODUCT CAPABILITIES
What’s in scope.
01
Transaction integration
Connect the transaction information supported by the configured ZRA integration. The deployment needs to establish which sales and purchase scenarios apply and how each is represented in the business process.
02
VAT and transaction records
Use the underlying transaction data within the configured reporting workflow. Finance teams retain responsibility for checking tax treatment and reviewing the information being transmitted through the connector.
03
Audit trail and visibility
Maintain records of the transactions handled through the integration. This gives the team a basis for reviewing submission activity and investigating entries that need correction or follow-up.
04
Environment and entity scope
The published offer includes cloud and on-premises deployment options and multi-entity support. Compatibility and the entity setup need to be confirmed against the actual Business Central environment.
Configure, test and assign ownership
Braintree’s published implementation approach includes environment setup and ZRA validation testing before go-live. The scope should cover representative transactions, required credentials and responsibility for monitoring the reporting process.
✓
Confirm supported transaction types and the company scope.
✓
Establish access to the required ZRA services.
✓
Validate the configured submission process with representative data.
✓
Assign ownership for reporting review, exceptions and ongoing support.
01
Create a reviewable submission process
The ZRA Smart Invoice Connector described by Braintree integrates supported sales and purchase activity from Business Central with the Zambia Revenue Authority process. The operational guide explains that posting creates integration entries and background job-queue work. The entry records what has or has not been processed, with statuses and messages that can be inspected when something requires attention.
This gives the finance and application teams a shared place to trace a document. The implementation should identify which companies, transaction types and service provider are in scope. The detailed Help material includes provider-dependent functions and Fiscal Edge references, so a deployment should not be described as independent of a service provider without specific confirmation.
02
Map the codes before sending transactions
The documented setup includes an API key, SDC identifier, environment settings, user permissions and the extension licence. Production and sandbox settings are separated, with live activation prevented in a SaaS sandbox. The guide also covers mapping VAT types, VAT product posting groups, VAT posting setup, reason codes and payment methods to the integration’s required codes.
Items are registered through a ZRA Item Worksheet before relevant documents can be submitted. The worksheet requires the mapped item category, product type, VAT category, units of measure and country of origin, with a recommended retail price where the configured VAT type requires one. This makes data preparation part of the implementation, not a task deferred until the first rejected invoice.
03
Check the document before the background job
The guide describes checks on invoices and credit memos for sales and purchases. These include the payment method, the applicable VAT mapping and the relevant Smart Invoice information on purchases. Credit and return scenarios have additional document-application conditions according to the configured treatment. The team needs representative examples from its own transaction flow to validate these requirements.
After posting, an integration entry and scheduled work track the submission. The Help guide also describes provider-dependent purchase-document import and creation, and a stock-export function that applies to the documented Fiscal Edge configuration. These are conditional capabilities: the selected provider and implementation must support them before they are included in the agreed scope.
04
Treat a status as an action cue
The troubleshooting guide distinguishes New, Validation Error, Job Queue Created, Error, Error Acknowledged and Success. A validation error occurs before a processing job is created; an execution error occurs when the job runs. That distinction helps the support team decide whether it needs to correct source data, inspect the connection or review scheduled processing.
The entry provides navigation to the source document and access to status details and request information. The guide describes resubmission actions, but those actions must be used with an understanding of the existing result. In particular, recreating a successful entry produces a new copy for processing. Review of the original submission evidence should therefore precede any repeat action.
05
Include customs and support responsibilities where needed
The documented customs function retrieves pending imports, lets a user associate line items and record approval or rejection, then submits the selected action. If the organisation needs that process, it should be tested separately from routine sales invoicing.
Confirm the provider, company scope, credentials and supported extension release.
Map tax, item, unit-of-measure, reason and payment codes using reviewed master data.
Validate invoices, credit notes, purchase scenarios and customs actions where applicable.
Assign responsibility for job queues, validation failures and submission review.
Agree how completed entries are retained or cleared and how support investigates exceptions.
EVIDENCE & DOCUMENTATION
See the work in context.
Documented integration entries and job queues
The operating guide explains item registration, document checks, background processing and provider-dependent functions. The troubleshooting guide defines the statuses used to investigate exceptions.
Explore the documentation
BEFORE YOU DECIDE



