Posts tagged: Medat

We have discussed the subject of “sales tax” internally and can provide you with a solution for private billing 1.7.2020 (ASCII, XML) if required. This consists of an update and an additional table to be maintained by your company, in which the information relevant for versions is stored in five columns (example see below). The VAT must be entered here in the cost unit. We need an own cost unit.
This definition table will also be used for the collective invoice. In all probability, we will be able to provide an update with a solution in mid-July at the earliest. The collective invoice program will use the same table for versioning the VAT rates. Please determine, independently of us, the cost units you are using, which are generated with a VAT rate and are used for VAT-charged invoices (collective, private invoices). If you do not have this yet, please create the cost units with us. There should be an entry in your table for each cost unit (analogous to the last three sample lines).

In the current program versions for 3.7, it will not yet be possible to mix different tax rates (19%, 16%) on one invoice. Therefore, the relevant billing periods should be selected accordingly if this condition occurs. The respective program will check for this condition and should terminate with a message if such a condition occurs.

We would like to draw your attention to the fact that the offsetting of VAT occurs most frequently in the collective invoice. There, however, the date is printed appropriately delimited anyway. Only latecomers in billing (subsequent change from “private” to “collective bill) can cause problems here and force a separate bill after the transition.

This means: You must always enter “07/01/2020” for future collective invoices with the “from date”.
Latecomers from previous quarters must then be billed separately, for example through “01/01/2020 – 06/30/2020”.

Private orders that have to be charged with VAT are usually individual orders that do not result in any excess within an invoice. Private invoices with different tax rates (based on the time of acceptance or import) processed within a billing run (XML private billing: “Ticket”) are no problem and should be appropriately assigned to the versioning.
If the order data of the same private invoice requires different tax rate versions, the program will issue a warning (XML private billing: red cross at the end of the ticket line), name the patient with errors in the error text, exclude them from the current billing, but generally continue the billing.

The patient must then be treated separately over a time division.

Please also clarify with your accounting department what exactly you need for the changeover.

We ask you to carry out the tests of the programs necessary for the update as soon as possible and on your own, as the short deadline requires quick action.
Changes to layouts will probably also be necessary in which the tax rate appears as a text constant in the layout. This applies to all billing variants. These text constants are replaced by the tax rates used in the case.

Our accounting colleagues will be happy to answer any questions you may have.