On this page
Define the records and direction
Describe which system owns each record and what needs to move. Examples may include approved sales information from a website, a customer reference from a CRM or a defined summary from a POS system. Feasibility depends on the source and destination capabilities.
Agree the integration behaviour
- Source and destination fields, identifiers and required masters.
- Transfer direction, timing and frequency.
- Permissions and credential handling.
- Duplicate prevention and amendment behaviour.
- Error logs, retry rules and exception ownership.
- Version compatibility and maintenance responsibility.
A successful transfer is not enough if incorrect or duplicate data enters the books. Define the review and reconciliation outputs alongside the connection.
Test before daily processing depends on it
Use representative records and realistic exceptions. Agree how missing masters, invalid values, interrupted transfers and source amendments should be handled. Identify who approves the outputs before deployment.
A one-time transfer may be better handled through migration or Excel import. Business-specific screens and reports may require TDL customisation.
Frequently asked questions
Can you connect any application to Tally?
No universal compatibility is promised. We review available interfaces, permissions, record structures and operational requirements before confirming feasibility.
Is an ASP connector the same as a general API project?
It must be assessed against the provider’s supported route and current requirements. Do not assume a general data connection performs accredited exchange or reporting.
Who maintains the integration after changes?
The proposal should identify the responsible parties and the process for releases, interface changes and additional requirements.
Bring the source and the expected result
Discuss an integration with BlackCat using a redacted example of the records involved.