Die teljesitesigazolas unterschreiben lassen und die Periode in Rechnung stellen

Record the contract, its Ptk. 6:130 payment regime and the dates it turns on, so every later step reads the same terms instead of somebody's memory of them.

Warum: A payment regime that lives in a PDF nobody opens is a regime that gets applied differently by each person who applies it. Registered once, the deadlines below are computed rather than argued about.

Record what was executed against each tetel for the period as a percentage of its contract quantity. The earned quantity follows from that percentage and the design quantity, and the earned amount from the same percentage and the position total, so one honest number per line produces the whole valuation. Keep potmunka on its own tetel rather than inside an existing one. A certifier who has to decide the whole period in order to decide the extra will decide neither. Where the contract settles on measured quantities, the decree on construction contracting has them kept in the felmeresi naplo of the e-epitesi naplo, so the percentages here should be the ones that log can back.

Warum: A teljesitesigazolas built from a single project percentage cannot be checked and therefore cannot be approved without a conversation. Measured line by line, the disagreement is about one tetel rather than about the whole month, and the rest of the money moves while that one is settled.

Route the teljesitesigazolas to the muszaki ellenor, and to whoever the contract adds after them. Keep the approval date, because the szamla follows the approval and the payment clock runs from there, so an approval that slips moves everything behind it. The decree on construction contracting gives the muszaki ellenor fifteen working days from your written notice that the performance is complete to issue the teljesitesigazolas or refuse it with reasons, and the szamla cannot lawfully be issued before it, so record the day the notice went in: the fifteen days run from it.

Warum: Approval sitting in an inbox is the most common reason a payment is late, and it is invisible while it is happening because nobody has refused anything. A route with a date on each hop turns that into a question with an owner instead of a monthly complaint. A certificate that is refused and a certificate that has simply not arrived look identical from the contractor's side, and the remedies for them are different. Recording the submission date is what tells the two apart.

Raise the szamla against the approved teljesitesigazolas, carrying visszatartas and any deduction the contract provides for, and reference the teljesitesigazolas on it. Between domestic VAT-registered businesses the reverse charge applies to construction and installation work on a property that needs a permit from, or a notification to, any authority, so the szamla carries the words forditott adozas and no tax, the customer accounts for the twenty-seven percent, and the invoice is reported to NAV online at issue like every other.

Warum: A demand for a figure nobody approved is one that will be returned, and the clock does not start on a returned document. Matching it to the teljesitesigazolas also means the accounts and the valuation tell the same story at year end without anybody reconciling them by hand.

Open a clock over the szamla starting from the day the szamla is received, under Ptk. 6:130. Payment falls due 30 days later, and the clock records that date rather than leaving it to be worked out when somebody asks. The module carries this period as the EU late-payment regime, which is the directive Ptk. 6:130 transposes, so pick that regime and count from the day the szamla arrives. Thirty days is the default; a business-to-business contract may agree longer, and past sixty days the term is presumed unfair, so where the contract sets its own date enter that date instead.

Warum: The single most expensive mistake in interim payment is starting the count on the wrong event, because every deadline behind it inherits the error and none of them look wrong. Anchoring on the day the szamla is received once makes the whole chain checkable.

Read back the dates Ptk. 6:130 produces from the day the szamla is received. The sum payable leads, the due date and the final date for payment sit under it, and the derivation spells out each date against the provision it came from, so every one of them can be quoted rather than asserted.

Warum: Deadlines that are typed in are deadlines that are typed in wrong, and a payment regime has more of them than anyone holds in their head. A derivation you can read out loud is what turns a phone call about a late payment into a quotable line.

When the clock has run out, take it to the Teljesitesigazolasi Szakertoi Szerv and preserve the claim. The record the steps above produced, dates, approvals and the documents themselves, is the case, and it is assembled already rather than reconstructed under time pressure. The expert body can be asked when the certificate is refused, when it never arrives and when it was issued and not paid; it answers within thirty days, sixty at most, and a court asked to enforce its opinion afterwards hears the case out of turn.

Warum: The difference between a claim that is paid and one that is argued about is almost never the merits. It is whether the dates and the documents were kept as the work happened, because reconstructing them afterwards is expensive and looks exactly like inventing them.