Yuki - Chift

Introduction

Yuki is a cloud accounting platform for businesses in Belgium and the Netherlands and their accounting partners. It covers bookkeeping, invoicing and bank reconciliation, and centralizes financial data between a business and its accountant. In the Netherlands, it has been sold as Nmbrs Accounting since 1 September 2026.

Activate Yuki

Partner keys

You can use Chift’s app, or register your own with Yuki.

Use Chift's app

Chift fills in the Client ID and Client secret fields for Yuki’s Purchase web service.

Use your own app

Email support.accounting@nmbrs.com to request a Purchase web service Client ID and Client secret, then enter them yourself in the Client ID and Client secret fields.

These keys are only needed to push purchase invoices. Every other feature works with the end user’s own Yuki webservice API key alone, as described in Connect Yuki.

Activate Yuki in your Chift account

In Connectors, enter your Client ID and Client secret.

Connector settings

Allow to push purchase invoices turns on Yuki’s Purchase web service, so purchase invoices can be pushed through the connector.

Yes: shows the Client ID and Client secret fields. Enter the Purchase web service credentials issued by Nmbrs Accounting, as described in Partner keys.
No: purchase invoices cannot be pushed.

Choose Yes to push purchase invoices. The end user’s domain also needs a bundle that includes the Purchase web service, as described in Vendor fees.

The Which clients and suppliers to return setting in the Chift connector settings, with its options All contacts and Only contacts with a booked invoice

Which clients and suppliers to return controls what GET /accounting/clients and GET /accounting/suppliers return. Yuki marks a contact as client or supplier only once a sales or purchase invoice is booked on it.

All contacts (default): both lists return every contact of the domain. Each list reads all contacts, one Yuki call per 100 contacts.
Only contacts with a booked invoice: each list returns only the contacts Yuki marked as client or supplier, with far fewer Yuki calls. A contact created through Chift appears once its first invoice is booked. A search by name or code, or a read by ID, still finds it.

Choose Only contacts with a booked invoice on domains with many contacts, to stay within the daily quota described in Rate limits.

Test Yuki


Environment	Sandbox account
How to get it	Ask your Chift point of contact for access to Yuki’s shared sandbox domain. Access is granted on request and subject to usage conditions, since it is a shared testing environment.

Vendor fees

Software editor (you)

No fees.

End user

Depends on the domain’s bundle. On the Minimal bundle, pushing sales invoices needs the Sales web service feature, billed to the accountant’s office at €10.50/month. Pushing purchase invoices needs a Minimal, Small, Medium, Large or Unlimited bundle.

Connect Yuki

Yuki setup guide for end users

The full step-by-step, with screenshots.

Before they start, your end users need:

a Yuki account with the Management or Backoffice role in the domain. Only these roles can create a webservice API key, under Settings > Integrations > Web services.
to grant the key All web services access.
a key of type Domain to connect several administrations. Otherwise, a key covers one administration.
to push purchase invoices, a domain on a Minimal, Small, Medium, Large or Unlimited bundle.
on the Minimal bundle, the Sales web service feature to also push sales invoices, as described in Vendor fees.

To connect, they:

paste the Yuki webservice API key into the connection form
optionally, select which accounting folder(s) to connect

Rate limits

Yuki applies a daily quota: 1,000 calls a day per domain by default. To increase it, a user with the “Portal administrator” role in the accountant portal can add one of the following accountant features to the domain, billed to the accountant’s office:

Yuki Webservice: up to 5,000 calls/domain
Yuki Webservice extended: up to 10,000 calls/domain

When the quota is hit, Yuki returns HTTP 500 with a “daily limit exceeded” error. Chift does not retry: it returns ERROR_RATE_LIMIT (HTTP 429) until the quota resets. Listing clients or suppliers reads every contact of the domain by default, one call per 100 contacts. On large domains, set Which clients and suppliers to return to Only contacts with a booked invoice, as described in Connector settings. See Yuki’s web services documentation.

Limitations & specificities

Attachments

Chift does not attach documents to journal entries in Yuki. A pdf field sent to POST /journal-entries is accepted but ignored, and the attachment status is returned as attachments_info.status: "unknown".Attaching a PDF to an existing invoice is available on request.GET /attachments returns only the files stored with the entry or invoice in Yuki. Yuki also archives the import file (XML or CSV) of every document Chift pushes. Chift leaves that file out.

Journals

GET /journals returns the document tabs of the archive folders that Yuki processes, and the bank accounts of the chart of accounts as financial_operation journals.Chift sets the journal_type of a tab from the first digit of its 3-digit ID. IDs starting with 1 are supplier_invoice, IDs starting with 2 are customer_invoice, and IDs starting with 3, 4, 5, 7 or 8 are miscellaneous_operation. This type does not show whether Chift accepts the journal. Chift accepts only these journals:

Document	Journal
Supplier invoice, supplier refund	`101`
Customer invoice, customer refund	`201`
Journal entry	`805`

Financial entries use the financial_operation journals. Each one is a bank account of the chart of accounts, and its journal_id is the account number.When a user must choose a journal for a document, show only the journal listed for that document.

Journal entries

Rules on journal entries in Yuki:

Lines use a general ledger account, or a customer or supplier account with force_general_account set.
Ledger accounts starting with 10xxx, 11xxx, 120xx, 125xx, or 15xxx cannot be used.
Entries are always posted to journal 805, in EUR.

Invoices

A customer invoice needs an invoice number when a PDF is attached.
A supplier invoice always needs a PDF attached.
Supplier invoices and supplier refunds must use journal 101.
Customer invoices and customer refunds must use journal 201.
journal_id is optional. If you send it, Chift checks it against these rules. Any other journal returns an error.

Chart of accounts & VAT

National, European and international VAT codes cannot be combined on one invoice. Use only one category of VAT codes per invoice.

Analytics

An invoice can only use one analytic account and one analytic plan.An analytic account’s name must be unique, and it cannot be updated once created.

Coverage

Troubleshooting

Specific errors for Yuki:

Error Code	Error description	Resolution
ERROR_ACCOUNT_NUMBER_NOT_GOOD_SCOPE	Journal entries cannot use ledger accounts starting with 10xxx, 11xxx, 120xx, 125xx, or 15xxx in Yuki.	Use a compatible account number for journal entries.
ERROR_CONNECTOR_MAINTENANCE	Yuki failed on its side (a `soap:Server` fault). Chift returns HTTP `503`, with Yuki’s fault message as the error detail.	Retry the request later. The same request goes through once Yuki recovers.
ERROR_CUSTOMER_INVOICE_PDF_REQUIRED	An invoice number must be specified when attaching a PDF on customer invoices in Yuki.	Provide an invoice number when creating a customer invoice with an attachment.
ERROR_INVALID_BODY	A journal entry line on a customer or supplier account needs `force_general_account` in Yuki.	Use a general ledger account, or set `force_general_account` on customer and supplier lines.
ERROR_INVALID_BODY	You cannot update an analytic account name in Yuki. Yuki also has a uniqueness constraint on the ‘name’ attribute for analytic accounts.	Avoid updating analytic account names and ensure analytic account names are unique.
ERROR_JOURNAL_NOT_ACCEPTED	The journal is of the right kind but is not the one Chift posts to, for example `You can only create a 'supplier_invoice' in journal_id '101' in Yuki.`	Use journal `101` for supplier invoices and refunds, `201` for customer invoices and refunds, and `805` for journal entries.
ERROR_JOURNAL_NOT_GOOD_SCOPE	The journal cannot be used for this scope in Yuki.	Use a journal that is compatible with the requested document type.
ERROR_SUPPLIER_INVOICE_PDF_REQUIRED	You need to attach a PDF when creating a supplier invoice in Yuki.	Attach a PDF when creating supplier invoices.
ERROR_WRONG_TAX_CODE_COMBINATION	National, European, and international VAT codes cannot be combined in one invoice in Yuki.	Use only one category of VAT codes per invoice (all national, all European, or all international).
ERROR_YUKI_ANALYTIC_DISTRIBUTION	Using multiple analytic accounts or analytic plans in a single invoice is not allowed in Yuki.	Use only one analytic account and one analytic plan per invoice.
UNEXPECTED_YUKI_ERROR	Yuki rejected the request. Chift returns HTTP `400`, with Yuki’s fault message as the error detail, for example `soap:Client: Unknown petty cash account 11000: Checking account`.	Correct the request using the message in the error detail.