Send documents from your software to Yuki
A Yuki integration focuses on sending documents to the right administration. We identify which documents come from your business software, what context needs to accompany them and who follows up. The Belgian Yuki API documentation describes web services for document delivery and archive exchange; we confirm the available route and permissions for your account.
For broader decisions about financial software and document flows, see Accounting integrations.
What information should accompany each document?
Your accountant confirms which documents and additional details are needed, where they originate and how they should be identified in the accounting records. We then assess what the software and selected Yuki route can provide.
Part of the transfer
Decision to make
Yuki
Documents
Decision to make: Which document group is in scope?
Context
Decision to make: Which reference or additional details are needed?
Source
Decision to make: Which tool manages the original document?
Follow-up
Decision to make: Who checks a complete submission and handles exceptions?
Yuki
Documents
Decision to make: Which document group is in scope?
Context
Decision to make: Which reference or additional details are needed?
Source
Decision to make: Which tool manages the original document?
Follow-up
Decision to make: Who checks a complete submission and handles exceptions?
Yuki
Which access and administration are involved?
We coordinate with your accountant or Yuki account administrator to identify the relevant administration, who can grant access and which permissions are needed. Yuki distinguishes portals, domains and administrations, so we confirm where the information belongs instead of assuming access is already in place.
Who handles an incomplete or unclear document?
Agree who adds missing context and where questions should go. We check what receipt or error information the selected route makes available and what your team does with it. The connection does not make accounting decisions; your accountant determines how submitted documents are checked and processed.
How do we assess document delivery to Yuki?
We agree with your accountant which document group, administration and context are required. Then we check the source software, Yuki access and current conditions for the selected route. We decide who reviews incomplete submissions and what follow-up is needed. This keeps the technical work and your accountant's responsibilities clear.
Map documents and context
Map the documents, source software and required context.
Check administration and access
Check the administration, account rights and available route.
Agree on follow-up
Agree how missing information and exceptions are handled.
Set the scope
Define the data flow, responsibilities, price and schedule in the proposal.
What affects the cost of a Yuki integration?
The price and schedule depend on the source software, document group, required context, account rights and follow-up. Existing connections and access through your accountant also matter. We check any Yuki web-service fees and current charges for your administration, then include relevant recurring costs in the proposal.
Common questions
Yuki's Belgian documentation describes web services for document submission and archive exchange. We check whether the selected route fits your administration, account permissions, source software and current terms.
Yes. Involve your accountant or account administrator in the administration, access and document requirements. They can confirm what information is needed and who follows up on submissions.
We do not assume that from the product name alone. The outcome depends on the document, context, available Yuki route and your accountant's process. We agree where a person still needs to review the information.
Which documents should reach your Yuki administration?
Tell us which software creates the documents, which Yuki administration is involved and who should review the submission. We can then discuss the route to assess.