Accounting software is most useful when the way you use it matches how the business operates. Recording sales, collecting documents and reconciling payments needs a consistent process, regardless of the system. EPOS Accountancy can discuss the software support needed for your bookkeeping or reporting engagement and confirm compatibility before accepting work.

You may want help understanding a records workflow, reviewing an existing setup or identifying why balances are difficult to reconcile. The first step is to describe the platform, the problem and the output you need. We check that the proposed work is compatible with the systems you use.

Agree the support task

Depending on your software platform, support can include reviewing the current workflow, configuring agreed accounting categories or explaining a defined process to your team. Migration, integrations and detailed troubleshooting need their own scope and suitability check.

RequirementPossible deliverableBoundary to confirm
Workflow reviewPractical process and issue listSystems and tasks covered
Accepted setup workSpecified configurationApprovals and opening information
Team guidanceAgreed walkthrough or instructionsTopics, attendees and follow-up
Data transfer enquiryDefined migration proposal if suitableChecks, data responsibility and exclusions

A subscription, a software licence and ongoing vendor support are not automatically part of an accountancy engagement. The proposal should identify who pays for software, who controls the account and which support requests are included. Any changes that affect historical data require clear agreement.

What you need to provide

Tell us which platform and connected systems you use, how transactions enter the records and what is going wrong. We may need sample documents, relevant balances and a description of existing processes. Access should use agreed permissions rather than sharing personal passwords.

You confirm business requirements and approve changes assigned to you. Where a vendor or another technology provider needs to resolve an issue, we agree any coordination rather than assuming it is included. The quality and completeness of source data remain important even when processing is automated.

Review before changing the system

We clarify the problem, confirm the work involved and review the existing workflow. After agreeing the task and fees, we carry out the accepted work and check the specified outputs. Handover explains the new process and any unresolved issues. Additional training, migration or recurring support is included only where agreed.

How this works in practice

Imagine a business importing sales from one system while entering the same invoices manually. A workflow review could identify the duplicated process and propose an agreed correction route. Historical corrections and integration changes would be separately scoped if needed. This illustrates a potential review, not a guarantee that any particular integration is supported.

Describe your software issue

Tell us the platform, the process involved and what you want to achieve. We can confirm whether suitable support is available.

Not automatically. We review the current arrangement and confirm whether it can support the accepted work before recommending changes.

Migration requires a specific capability check and proposal. The records, validation work and responsibilities need to be clear.

Only when agreed. A defined walkthrough can be scoped by topic and audience rather than treated as unlimited support.