Compliance: obligations, filing evidence, and month-end checks

Open Compliance from the app launcher after selecting the relevant organization and entity. Confirm the country, registrations, period, and the person responsible for the obligation.

The available obligations and filing workflows depend on jurisdiction and account configuration. A general compliance calendar or prepared report does not mean electronic filing is supported for every authority.

Before starting, collect the records needed for the particular return or check. Ask your accountant to confirm eligibility, due dates, and statutory treatment where there is uncertainty.

Use the obligation's own screen and evidence requirements.

1. Find the relevant obligation or calendar item and verify the entity, registration, and period.
2. Review the underlying accounting records and complete the relevant reconciliation.
3. Resolve missing data and validation errors before preparing the final output.
4. Follow the supported review and submission process for that obligation.
5. Retain the submission reference, acknowledgement, and result.
6. Check the final status and follow up on a rejection or pending response.

Preparing a return creates information for review. Submitting sends it through the supported filing channel. Acceptance or acknowledgement is the authority's response. These stages should not be treated as interchangeable.

If the app or network fails during submission, check the existing submission status before trying again. Keep the original reference so support can trace the result. Do not mark a filing complete only because a file was downloaded.

The app includes compliance, reconciliation, and month-end areas. Use them to organize the applicable checks, but review the underlying documents when balances disagree.

For a month-end review, compare bank activity, outstanding receivables and payables, relevant tax balances, and the reports for the same period. Explain unresolved differences and retain evidence of review according to your organization's process.

Illustrative example: an accountant-approved reconciliation for one supported obligation and period shows a reportable amount of 1,000. The prepared output also shows 1,000. This agreement checks the amount; it does not establish that the obligation was submitted or accepted.

If a supported submission returns a reference but the result is pending, retain the reference and check the current status through the applicable workflow. Do not describe the filing as accepted or submit a second time simply because the final response has not arrived.

If the prepared output instead shows 1,100, investigate the 100 difference by checking the period, registration, included transactions and applicable adjustments before submission. The sample amount is fictional and does not define a tax rate, legal deadline or country-specific filing rule.

A completed check retains the source reconciliation and, where filing applies, the submission reference and authority's actual response. For an uncertain status or unexplained amount, email hello@hellobooks.ai with the jurisdiction, obligation, period and references, and ask your accountant to resolve statutory interpretation.

Email hello@hellobooks.ai with the jurisdiction, obligation, entity, period, filing reference, exact status or error, and the action you attempted. Include a redacted screenshot or validation report where helpful.

Do not send passwords, one-time codes, signing credentials, or secret keys. Support can explain the next step without those credentials. Tax interpretation and filing eligibility should be confirmed with your accountant.