Braintree Pivot
Built around the work.
Banking and finance with fewer handovers
ABSA and FNB integrations connect payments and banking activity with Business Central. Trade tools support supplier reconciliation, customer collections and import costing.
Documents where the work happens
DocuVault connects Business Central documents to SharePoint. Governance tools help teams manage procurement evidence, document ownership and expiry status.
CAPABILITIES
What it brings together.
01
Banking
•
ABSA Bank Integration
•
FNB Bank Integration
02
Tax processes
•
ZRA Smart Invoice Connector
•
ZIMRA VAT Connector
03
Governance
•
DocuVault
•
Preferential Procurement
•
Compliance Document Tracker
•
Extended Workflow
04
Operations
•
Inventory ScanCapture
•
Trade Assistant
•
LightPOS
•
FastTrack
Trade Assistant: finance and logistics modules.
01
Vendor Reconciliation
Match supplier statements to accounts payable, identify discrepancies and prepare payment information.
02
Debtors Collection
Review balances and ageing, record collection conversations and schedule follow-ups.
03
Forward Exchange Contracts
Apply the relevant exchange rate to receipts for consistent procurement costing.
04
Landed Cost
Published scope covers allocating import costs to goods. Confirm the current production release; the Help page remains marked pre-release.
DocuVault: documents linked to Business Central records.
Use SharePoint for document storage while keeping files accessible through Business Central. The aim is to avoid inflating the ERP database with embedded documents and make documents easier to find from the record that uses them.
FastTrack: prepare the setup and migration.
Reference data, migration templates and quality checks support company setup and data migration, leaving more attention for testing, training and process decisions.
PROJECT CONTEXT
Choose extensions against a real workflow.
Identify the handover or manual task, confirm the Business Central version and integration requirements, then test the extension with the people who will use it. Decide which modules are needed before scoping deployment and support.
01
Find the step that standard configuration does not cover.
An extension decision starts with a complete transaction. Follow a supplier invoice from receipt through approval, payment and reconciliation, or follow imported stock from purchase order through final landed cost. Identify where users export data, repeat capture, chase evidence or calculate figures outside Business Central. The useful requirement is the missing step and its owner.
Compare that requirement with the standard Business Central function already configured in your environment. Then examine the relevant Pivot module, any existing third-party app and custom development. This prevents overlapping approval rules or two integrations trying to update the same record. An extension should have a defined role in the process and a clear system of record.
02
Define what crosses each integration boundary.
Extension area
Decisions to resolve
Banking
Confirm the participating bank service, account permissions, submission and approval responsibilities, rejected transactions and reconciliation evidence.
Document management
Specify the SharePoint location, document ownership, access permissions and the link between a document and its Business Central record.
Inventory and trade
Agree scanning workflows, item identifiers, units of measure, costing rules and the handling of reversals or incomplete data.
Tax connectors
Confirm the relevant registration, transaction types, required data, rejection handling and responsibility for reviewing submission status.
03
Make compatibility and exceptions part of acceptance.
Microsoft provides app management in Business Central, but an installed app still needs configuration and operational testing. Record your environment type, Business Central version, installed apps, customisations and integration endpoints. Confirm the selected Pivot module supports that combination before a production installation is scheduled.
Use a sandbox to test the ordinary workflow and its exceptions. For banking, include a rejected instruction and reconciliation. For documents, include a user who should have no access. For inventory, include a correction after scanning. Finance and operations owners should approve the resulting records, not only the appearance of the screen.
The handover should identify configuration choices, permissions, integration credentials, exception queues and the support contact for each dependency. Agree how Business Central updates and extension updates will be reviewed together. Your team remains responsible for source-data accuracy and business approvals; the implementation scope should make technical support and remediation responsibilities explicit.
BEFORE YOU DECIDE



