ケース / コマーシャルと契約
コマーシャルと契約

適法なXRechnungを発行する

完了した期間の出来高を、ドイツの公共発注者が実際に受理する電子インボイスに変える。規格が求める発注者・受注者データを整え、チェックが指摘するルールをすべてクリアし、XRechnungのXMLを出力して送付先を記録する。

7ステップ11 分総合建設会社専門工事業者コストコンサルティング会社 / 積算事務所

仕組みをステップごとに

プラットフォーム全体で7ステップ - 各ステップで何をするか、そしてなぜ重要か。

1

Take this period's positions off the bill

内訳書

Open the priced bill and work out what this interim actually bills: the positions finished on site in this period, measured rather than estimated, and the amount that falls on them.

理由: An interim invoice is a payment on account for work genuinely done. A position billed ahead of the Leistungsstand is the one the client's surveyor strikes out, and the rest of the invoice waits while that single line is argued.

入力Priced bill positionsSite measurement出力Amount to billBilling period
2

Raise the receivable invoice

財務

On the receivable side of the Invoices tab, raise the interim invoice with its number, invoice date, due date and one line per block of work it bills, and pick the client from the contacts rather than typing a name into a free text field.

理由: The electronic invoice is built from this record and nothing else, so a line missing here is a line missing in the XML. Picking the linked contact is what lets the buyer address be read instead of retyped on every invoice you send that client.

入力Amount to billClient contact出力Receivable invoiceInvoice lines
3

Complete the buyer on the contact

連絡先

Open the client contact the invoice bills and fill in the buyer party the standard wants: legal name, street, postcode, town and the two-letter country code. The electronic invoice reads the buyer from here, not from the invoice.

理由: An invoice whose buyer has no postal address is rejected outright, and for XRechnung the town and the postcode are each a fatal finding of their own. Filling them once on the contact fixes every invoice you will ever send that client.

入力Client contactBuyer postal address出力Complete buyer partyReusable master data
4

Fill the seller side once

設定

Under Settings, E-invoice, set your own side once: legal name and address, VAT identifier or tax number, a named contact with telephone and email, the IBAN the client pays into, and the payment terms you invoice on.

理由: XRechnung asks for more than the European standard does, and the named seller contact with a phone number and an email is exactly where it goes further. Set it here and it is right on every invoice afterwards, instead of being chased once a month.

入力Company registration dataBank account出力Seller identityPayment terms
5

Run the check until it is green

財務

Open the electronic invoice dialog on that invoice, pick the XRechnung profile, and read what comes back. Blocking findings quote the rule identifier that will reject you, BR-DE-15 for a missing Leitweg-ID among them. Fix each one and run it again.

理由: This is the same rule set the receiving portal runs, quoted in the same words. Reading BR-DE-15 here costs you a minute. Reading it in a rejection notice three weeks later costs you the whole payment period and a second run at the invoice.

入力Draft electronic invoiceLeitweg-ID from the client出力Rule findingsGreen check
6

Export the XRechnung XML

財務

The download only unlocks once the check is clean. Take the XML: that file is the invoice. A hybrid PDF carrying the same data inside it is there for readers who want a page to look at, and it is not what the receiver parses.

理由: A public buyer's system reads the XML and ignores whatever you attached for human eyes. Sending a PDF and calling it an electronic invoice is the most common way a small firm finds out what the mandate actually asked for.

入力Green checkApproved invoice出力XRechnung XMLOptional hybrid PDF
7

Record where it went

電子請求書の認証

Log the send: the registration you issued under, the document itself, and the transmission id the portal or the access point gave back. The Leitweg-ID it was routed on is what the record keeps.

理由: Germany routes an invoice rather than clearing it, so no authority stamps yours. The transmission id is the only proof you sent it on the day you say you did, and it is what you quote when the client's accounts department cannot find it.

入力XRechnung XMLPortal receipt出力Transmission idSend on record
モジュール

このプレイブックのモジュール

プラットフォーム 190 モジュール中 5 個

The market this case is written for

ドイツ

Everything in this case follows how construction work is measured, priced and paid for in this market. The forms, the cost breakdown and the payment rules are the ones used there, not a generic version of them.

Standards it follows

  • DIN 276
  • GAEB XML
  • VOB/B

You do not have to set any of that up by hand. The first time you open the platform it asks which market you work in. Choose this one and it sets the interface language, loads the matching cost database and records the cost classification, and it adds an example project you can open straight away.

コマーシャルと契約の他のケース

コマーシャルと契約

Turn a change into a paid variation

Capture a scope change while it is fresh, price it as a contract variation on your agreed r…

3ステップ11 分開く
コマーシャルと契約

Run a subcontractor package

Award a trade package to a subcontractor, place it on a subcontract with a schedule of valu…

3ステップ11 分開く
コマーシャルと契約

Payment application and reconciliation

Value the work put in place this period against the contract, raise the application with th…

3ステップ12 分開く