Purchase cycle
You pay every fattura once,
and the distinta writes itself.
Duckday holds every fattura you receive, from the file that lands to the bonifico that leaves. What comes out at the end is a real distinta bancaria to upload to your bank, not a list of transfers somebody still has to retype into the portal.
Fatture arrive already read.
You load what your fornitori send you, one document or the whole month at once, and Duckday reads it: who issued it, for how much, against which scadenze and on which IBAN. A fornitore you do not have yet is created from the invoice's own data. One you had already loaded is set aside rather than turned into a second debt, even when the first copy was typed in by hand.
New fatture arrive with their payments already planned.
On each fornitore you decide once how they get paid: bonifico from a given account, Ri.Ba., RID, company card, or an advance from an employee. From then on every fattura from that fornitore arrives with a payment planned on each scadenza, and on the day a scadenza falls due its payment is confirmed. Change the rule later and what is already planned stays as you left it.
Set the rule once on the fornitore and every new fattura comes in with a payment waiting on each scadenza, dated and costed.
Treasury gets the file the bank is waiting for.
One view gathers the payments across every fattura, so whoever goes to the bank picks what leaves this week without opening documents one at a time. Choose them and Duckday writes the distinta bancaria for you, split by debit account and execution date, checked before it reaches your hands. Nothing counts as sent until the file has really been saved: prepare it, think better of it, and no payment shows as made.
What you owe sits beside what you are owed.
The same fatture feed the scadenziario di tesoreria next to the ciclo attivo, so the cash projection and the aging cover both directions instead of living in two products that do not speak. When the statement comes back from the bank, movements are proposed against the items still open. Every change stays on the record with who made it and when, and seeing the fornitore side is a permission of its own, separate from the customer side.
One cash projection holding both what leaves and what comes in.
Everything it does
- XML invoice importUpload FatturaPA XML, ZIP or .p7m: read automatically, duplicates set aside, outcome per file, or by hand.
- Supplier invoice registerInvoices, credit notes and self-invoices in one list, with amount due, instalments, notes and original file.
- Payments and CBI fileRecord payments, see them all in one view, and generate the CBI file with a receipt attached to each one.
- Supplier recordsCompany name, fiscal data and multiple IBANs per supplier; created from invoices, learns IBAN from payments.
- Automatic payment ruleSet once how a supplier gets paid: new invoices arrive with payments already planned on each instalment.
- Supplier spend dashboardCost by month and by supplier, the biggest suppliers, and documents broken down by payment status.
- Records from the business registrySearch the business registry and the card fills in with official data.
- Receivables and payables scheduleReceivables and payables in one view, by aging bracket, calendar or list.
- Treasury and bank reconciliationBank statement import (CSV, CAMT, CBI), suggested matches, cash projected on due dates.
Questions we actually get asked.
- Do the fatture reach us from the SdI on their own?
- No, and we would rather say so before you sign than after. You load the files you receive, one at a time or the whole month together, and you type a fattura in by hand when there is no file at all; we do not read PDFs or scans. Everything after that point is ours.
- What if a fornitore sends a nota di credito?
- You link it to the fattura it belongs to and its amount comes off what you owe, with nobody redoing the sum. Duckday only offers you documents that can genuinely be linked, so from a nota di credito you see the fatture from that same fornitore and nothing else.
- Is there an approval step before an invoice gets paid?
- Not as a workflow. There is no “to be approved” state and no approver: there are two levels, whoever can read and whoever can register and pay. The control is who holds that second permission, and the rule you set on the fornitore.
Works with
Tell us how you work today.
There is nothing to prepare. Half an hour on how your company runs — who tracks the hours, how an invoice comes together, when you find out whether a commessa made money — and we tell you which modules would fix it and what a quote looks like.