# Client document collection for year-end

> Client document collection for year-end: What's missing, wrong period, unreadable Checked: proven by code. Produces complete pack, client questions.

Source: https://www.sumarity.ai/library/client-document-collection-for-year-end/

Accounting, tax and Treuhand firms 

# Client document collection for year-end

Reads the year-end checklist, the client's uploads. Produces complete pack, client questions. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person.

Proven by codeDocuments, onboarding and KYC
Start from this workflowMore for accounting firms  

What it decides

## Narrow questions, each with a check behind it.

What's missing, wrong period, unreadable
Proven by code: document kinds and periods against the checklist. Code proves the answer from the data itself: totals tie, a match is exact, the quote is on the document. Most of these judgements settle without a person.

| Reads | The year-end checklist, the client's uploads 
| Produces | Complete pack, client questions 
| Who signs | A person on your team, with every figure traced to its document and every call on record 
| Process | Documents, onboarding and KYC 
| Industry | Accounting, tax and Treuhand firms    

See it run

## Every line, decided where it's safest.

An example run. Each stage lights up as a line is decided there; pick a stage to see its lines.

ReadsThe year-end checklist, the client's uploadsCodeReads, matches, ties out and works out every figure.JudgementWhat's missing, wrong period, unreadable. Settles only when it clears the cutoff and code proves it.A personGets whatever stays uncertain, with the evidence. Their ruling tunes the next run.ProducesComplete pack, client questions  
Client document collection for year-end · example run Example run  

| Ref | Item | Value | Decided by  
| DOC-1 | Bank statements, Jan–Dec12 of 12, all accounts |  | Code · complete 
| DOC-2 | Payroll year-end summaryReceived, covers the year · 0.97 |  | Engine · proven 
| DOC-3 | Pension statementLast year's statement, not this year's |  | To a person 
| DOC-4 | Car logMissing |  | To a person 
| DOC-5 | Loan confirmationBalance matches the ledger |  | Code · tied  
|  

Settled 3 To a person 2 Settled wrong 0      Illustrative lines. Amber rows are the Judgement Engine's calls; each settles only above its cutoff and when its check agrees.    

What it could save

## Your volumes in. Your hours out.

In our tests, between 24% and 42% of items still went to a person after tuning. Set your own share; a pilot measures it on your data.

Items per run 
Runs per month 
Minutes per item by hand 
Cost per hour

Share of items that still need a person: 30%  

By hand today80 ha month 
With Sumarity24 ha month, for the items people decide 
Saved56 hCHF 53,760 a year    

Related

## Start from what's closest.

### Documents, onboarding and KYC in other work

Accounting firms

### Client onboarding: AML and engagement checks

Identity, beneficial owners, risk rating

Cross-checkedBanking

### Corporate KYC onboarding

Beneficial owners, documents complete, risk

Cross-checkedBanking

### Periodic KYC review

What changed; whether risk changes

Cross-checked

### More for accounting firms

### UK VAT return for a small business (pub VAT)

Each document's VAT treatment; what's missing

Proven by codeTested

### Swiss VAT (MWST) return

Rate and method per line; input tax recoverable

Proven by code

### German VAT advance return (USt-Voranmeldung)

Treatment per line, reverse charge

Proven by code  

Questions

## What buyers ask

What happens when Sumarity isn't sure?

Nothing settles below the cutoff, or when the check disagrees. The item goes to a person in the inbox with what the engine saw, its best answer and the runner-up. The person's ruling is kept and tunes the next run.

How are its judgements checked?

Code proves the answer from the data itself: totals tie, a match is exact, the quote is on the document. Most of these judgements settle without a person.

Can we change it to fit how we work?

Yes. Start from this workflow and describe your differences in plain words. The design assistant revises it, the validator checks it, your expert reviews it on the canvas, and your admin publishes it.

Does it read our files as they are?

Yes: spreadsheets and CSV in any layout, PDFs, bank formats and e-mail attachments. Sumarity suggests how each column maps, proves the mapping on a sample and remembers it once a person confirms it.

Where does our data go?

Sumarity runs in Zurich. Your data, backups and logs are stored in Switzerland.

How does it get better?

Your team's rulings become an answer key. Better questions and cutoffs are proposed, tested on data they haven't seen, and published only when your admin approves. It improves itself, with permission.

## Start from this workflow. Run it on your data.

A pilot runs alongside your own process for a few weeks, at our cost, and ends in a line-by-line comparison.

Talk to usBack to the library