Jump into the policy in question and head to the money tab. At the bottom you can can remove records from Digit:

When a payment is taken by card in DigiT, the system records the payment immediately against the policy and allocates it according to the scheme’s configured payment flow.

• Card payments are treated as received at the point of authorisation.
• The timing of when insurers are payable and when commission can be withdrawn depends on:
  Site-level accounting settings
  Any scheme-level overrides
• Once processed, the payment will appear in the bank accounts area under SchemeServe transactions. It will bypass the ledger tab as it will automatically be marked as recieved.

*If you have 2 bank accounts, this will automatically land in the default account.

When a policy is cancelled, SchemeServe automatically recalculates the premium, commission, and insurer balance based on the cancellation terms.

• Any return premium due is calculated at the point of cancellation.
• If funds have already been collected, Digit determines whether:
  A refund is due to the customer, or
  An accounting adjustment is required.

Refunds and adjustments are processed in line with:
- Site-level accounting settings
- Scheme-level configuration
- Applicable tolerance limits

If the insurer or agent has already been paid, Digit manages the difference using adjustments or balances rather than reversing historic transactions.

This approach ensures cancellations and refunds are handled accurately while maintaining accounting integrity.

Yes, to get to the appropriate page, you need to go to the ‘Accounting‘ tab, and then click ‘Accounts Payable’ tab.

1. First you need to find the insurer the payment needs to be paid to. To do this, on the Accounts Payable table search the insurer from the Transactors filters on the top left. You will then see a list of case records broken down by riskgroups appear, associated with this insurer/agent.
2. You can then further filter these cases using the search in the top right of the table by ‘Case Id, Record Id or Money out).
3. The amount that needs to be paid to this insurer, is calculated from the information given in the ‘Matrix’ tab on the case record itself. The Net Premium of this Risk Group, minus commissions.
4. Once you have found the case(s) you need, tick the box to the left of the case(s), and click ‘Record payment’ at the top right or in the footer displayed at the bottom. This will open a smaller pop-up box headed ‘Record insurer payment‘.
5. Here select the ‘Payment Type‘ (Bacs, cheque, bank to bank…). This is a required field that MUST be set.
6. Insert the ‘Reference‘ from the cheque, or bank transaction underneath. This is a required field that MUST be set.
7. Add the Date that you received the payment in the date box below.
8. The ‘Payment amount’ is already calculated and cannot be changed.
9. The ‘Bank account’ selection allows you to select which account in SchemeServe you want to record the payment for where more than one account has been created in SchemeServe. If a payment has already been recorded for one or more of the cases selected, the account selected will need to match the account that this previous payment was recorded for.
10. You can add Notes about this payment. This is optional.
11. At the bottom you can expand the table to see all cases/riskgroups that have been selected and the individual amounts owed.
12. Click ‘Submit‘ – the payment can then be found in the bank account under ‘SchemeServe Transactions’

You will then need to ‘Reconcile‘ this payment in Accounting.

If a mistake is identified, the preferred and safest approach is to use an adjustment rather than editing live policy data.

• Do not edit a policy that is already on cover - Digit will not retrospectively update accounting or payment records.
• Where necessary, the payment can be removed from the Money tab in Digit. The policy can then be taken off cover, corrected, and placed back on cover.
• In most cases, doing an adjustment/MTA is the ideal solution and preserves accounting integrity.

Every scenario is different, so if you’re unsure of the correct approach, please contact our Obsessive Support team for guidance.

Once a policy has gone On Cover, it should not be edited.

Digit will not retrospectively update accounting, payments, or statements if changes are made to a policy that is already on cover. Editing at this stage can lead to discrepancies in accounting.

If a change is required:

• Use an adjustment where possible (this is the preferred approach), or
• Remove the payment from the Money tab, take the policy off cover, make the required changes, and then place the policy back on cover.

If you’re unsure which approach is correct, contact our Obsessive Support team for guidance, as each scenario can differ.

Manual accounting entries are not currently supported in Digit.

We recognise that this functionality is of interest to many users and are actively researching how manual entries could be introduced in a future update.

In the meantime, adjustments and existing accounting workflows should be used to correct or balance transactions.

If payments appear to be missing in Digit, do not attempt to manually correct the figures.

First, check the Money tab to confirm whether the payment has been recorded but not yet allocated.

If Digit was enabled after the policy was placed On Cover it won't show in Digit. You may need to manually add it to Digit on the money tab.

Review the policy status to ensure it is correctly placed On Cover, as payments will not post correctly if the policy is off cover.

Confirm the scheme and site accounting settings, as payment flow and timing rules can affect when payments appear.

If the payment is still missing, please contact our Obsessive Support team with:

• The policy number
• Payment amount
• Payment method
• Date the payment was taken

This functionality is not supported at this time. All payments must be recorded by authorised internal users in line with Digit’s accounting controls.

We recognise that this capability is important for some workflows and is an area of active interest. We are currently reviewing how this could be supported in the future.

This functionality is not supported at this time. All payments must be recorded by authorised internal users in line with Digit’s accounting controls.

We recognise that this capability is important for some workflows and is an area of active interest. We are currently reviewing how this could be supported in the future.

No. Once an accounting period has been closed in Digit, it cannot be undone.

Closing an accounting period finalises all balances and transactions for that period to preserve accounting integrity. If an issue is identified after closure, it should be addressed in a subsequent open period using adjustments.

If you’re unsure how best to proceed, contact our Obsessive Support team for

The ledger uses the transaction (accounting) date, not the policy start, end, or cover date.

This is the date the financial transaction is posted into accounting (for example, when a premium, adjustment, or refund is created)

Yes. Digit supports part payments.

When recording a payment from the ledger, simply enter the amount you wish to record. The remaining balance will stay outstanding in the ledger until it is paid or otherwise adjusted.

This allows payments to be recorded over multiple transactions while maintaining a clear outstanding balance.

Currently, if you would like to write-off certain amount, you can do this at reconciliation. Therefor, you enter the full amount when recording the payment and then later write-off the other amount.

Not yet. Digit currently supports reconciliation on a line-by-line basis only.

We recognise that reconciling multiple lines together would be beneficial and this is an area we are actively exploring for future development.

When you switch agents at renewal, all existing records for the policy will be reassigned to the new agent. This may result in the new agent receiving statements that include outstanding amounts from the previous broker.

The recommended approach is to rekey the renewal onto a new policy, allowing the new broker to start with a clean policy record.

Once enabled, all payments should be administered in Digit as part of the standard training process.

Apart from external payments, there should be very little need to manually add payments directly to the case. The delete feature is intended to help reduce payment errors caused during training or incorrect entry.

If a payment has already been recorded and appears on the Ledger tab, it can still be deleted if required. However, deleting the payment will create a contra entry to offset the original transaction, rather than removing the financial history completely.

This is because payments are synchronised with Digit, and removing a payment after it has been processed will leave a negative amount against the record. Deleting a payment does not erase the transaction - it creates a balancing reversal entry for audit and accounting purposes.

Test Mode allows your team to safely explore and learn Digit without affecting live policy data.

How Test Mode Works

When a policy is placed “On Cover”, the policy data will still flow into Digit as normal. This allows you to test Digit using real policy information and realistic scenarios.

However, any actions completed within Digit while Test Mode is enabled are treated as dummy actions and are not written back to the live policy records.

For example:

• A payment can be recorded against a policy in Digit
• The payment will appear within Digit
• But the actual policy record will remain unchanged

In simple terms:

Data flows into Digit, but nothing flows back out.

What This Means for Your Team

Your team can safely:

• Explore the system
• Test workflows
• Record dummy transactions
• Learn how Digit operates

without any risk to live customer or policy data.

Test Mode means that the live policy will not be updated and payments will not be recorded. This means users will need to record payments from the policy to ensure financial admin is still kept up to date while Digit testing is ongoing.

Dummy Bank Account

A dummy bank account is configured while Test Mode is active. This can be updated to your live bank account details once training has been completed and Test Mode is removed.

Moving to Live Mode

Once training is complete, Test Mode can be disabled by SchemeServe. Test data must also be cleared.

 At that point:

• Actions completed in Digit will become live
• Payments and updates will affect real policy records
• Data will flow both into and out of Digit