Test-Approach

Testing is a crucial part of the setup process for integrating Accounting as a Service, providing a structured approach through key phases, responsibilities, and completion criteria to ensure system functionality and client approval before going live.

The overall objective is to test all relevant processes and interfaces, ensuring the client’s setup works correctly.
All testing phases aim to mitigate risks, detect issues early, and ensure a smooth go-live.

Test Phases Overview

You will go through the following test phases during the setup process of Accounting as a Service:

Internal Test: Verify the setup using internal data and ensure internal approval.
Sandbox-Test: Confirm that systems are connected and able to exchange requests.
UAT (User Acceptance Test): Test all features with all involved systems and obtain external sign-off.
FUT (Friendly User Test): Test the basic processes in the production environment to ensure everything is ready for go-live.

Typical Test Procedure

The following procedure outlines a typical test-scenario:

You will begin the test procedure by submitting test orders to Accounting as a Service.
These test orders will be processed within Accounting as a Service, which includes services such as capturing the payments, sending notifications, and processing settlement files.
You may also submit test goodwills or returns.
Accounting as a Service will handle refunds, notifications, and settlement files processing.
Once the test processes are complete, you will receive the subscribed notifications and end-customer communications for review.
During the testing, you can also confirm integrations with third-party providers, such as risk management systems.

The submission of the order is the foundation of the test, and the steps that follow depend on the features and scope you’re testing. This will influence the length and complexity of the process.

Communication During the Test Phases

You will have a dedicated contact person during the test phases. The tests are conducted asynchronously, and you can establish a communication channel before the test, depending on what is being tested.

We offer the following communication options:

Communication via email with all or selected participants
A dedicated Teams chat
Daily testing calls (depending on the test, it may be that we agree to have these calls on a weekly basis)

Test Specification

You will receive a standardized test plan from Accounting as a Service, which covers the most common test cases. However, you must review, adapt, and extend this plan if necessary to ensure that all required scenarios are covered for your business.

The test specification is a detailed summary of what scenarios will be tested and acts as the tool to measure whether the test phase is complete. A phase is considered successfully completed if all test cases have been executed at least once and no errors are detected.

Responsibilities

As the client, you are responsible for reviewing and signing off on the test phases. Additionally, third-party providers, such as payment service providers (PSPs) or banks, must be involved. For example, a settlement file from the PSP is required to ensure correct processing. You should also involve other third parties, such as risk management providers or collection agencies, to test those processes if they are part of your setup.

Phase-End Criteria

Each phase must meet specific criteria before you can move on to the next one:

Internal Test: Once Accounting as a Service internally confirms that the setup is functioning correctly, the phase is complete.
Sandbox Test: The phase is complete once you verify that systems are connected and can exchange requests and receive confirmed request-notifications.
UAT: This phase is completed when all payment methods and the settlement file process are successfully tested, and you provide external sign-off.
FUT: Once basic processes are verified in the production environment, this phase concludes with your approval to go live.

UAT Completion

During the User Acceptance Test (UAT), you will be required to test all the relevant features, including payment methods and settlement file processing. Completing this phase involves ensuring that each payment method and settlement process works as expected.

With your sign-off, you confirm the setup and take over reliability for all errors occuring in the production environment.

FUT Completion

The Friendly User Test (FUT) is your final opportunity to test the setup in the production environment. Since some features, like dunning and collection, cannot be fully tested during FUT, this phase focuses on basic processes. Your approval at the end of FUT is essential to move forward with the go-live.