improve desc of storno and references for dsfinv-k

doc/appendix-de-kassensichv/reference-tables/reference-tables.md

@@ -446,7 +446,7 @@ Each subitem as described in the table below:
 | `BON_TYP` | Receipt type / action type| String (30) | Deducted from `ftReceiptCase` |
 | `BON_NAME` | Additional description related to the `BON_TYP` | String (60) | Mandatory if `BON_TYPE` is "AVSonstige", otherwise optional, can be sent via `ftReceiptCaseData` in JSON format. To send, add the key value pair `ReceiptName ` e.g. `"ftReceiptCaseData":"{ ..., "ReceiptName":"Sonstige Sonderwurst", ... }"` |
 | `TERMINAL_ID` | Mandatory, ID of the terminal that was used to record this receipt | String (50) | `cbTerminalID` |
-| `BON_STORNO` | Cancellation indicator | String | Filled by ft. Mandatory: if the receipt is a reverse/voided receipt, then it must be marked with the `ftReceiptCaseFlag` `0x0000000000040000` and has to reference the initial receipt via `cbPreviousReceiptReference`. |
+| `BON_STORNO` | Cancellation indicator | String | Mandatory if your receipt is a reverse receipt that voids another, previous receipt. In this case mark your receipt with the `ftReceiptCaseFlag` `0x0000000000040000` and reference the receipt to be voided via `cbPreviousReceiptReference`. Ft will then set the `BON_STORNO` flag in the DSFinV-K export and will also add a corresponding reference in the file "**Bon_Referenzen (references.csv)**" (see below). |
 | `BON_START` | Time of the action start | ISO 8601 and RFC3339 date | The action start can be within this cashpoint or outside of this cashpoint. If outside (e.g. by another system or another cashpoint) than it has to be provided in via `ftReceiptCaseData` in JSON format by adding the key value pair `ActionStartMoment`. E.g. `"ftReceiptCaseData":"{ ..., "ActionStartMoment":"2020-09-27T17:00:01", ... }"`. If not provided, ft tries to find the action start by following the `cbPreviousReceiptReference` path into the past until no more previous receipt references exist. ft will than fill this field with the value from `cbReceiptMoment` of the oldest receipt found in that chain. |
 | `BON_ENDE` | Time of the action end | String | `cbReceiptMoment` |
 | `BEDIENER_ID` | User-ID | String (50) | Mandatory, send via `cbUser` in JSON format by adding the key value pair `UserId` e.g. `"cbUser":"{ "UserId":"19292", "UserName":"Peter Lux"}"`|
@@ -502,9 +502,11 @@ Each subitem as described in the table below:
 
 ##### File: Bon_Referenzen (references.csv)
 
-If `cbPreviousReceiptReference` is filled in the receipt request, ft will automatically try to find the referenced receipt and if found, ft will add an entry to Bon_Referenzen. For a recommendation on how to connect the single requests via `cbReceiptReference` and `cbPreviousReceiptReference` see our Business Cases Examples document [here](https://fiskaltrust.de/wp-content/uploads/sites/5/2020/02/fiskaltrust-Business-Cases-in-JSON_englisch.pdf).
+If `cbPreviousReceiptReference` is filled in your receipt request, ft will automatically try to find the referenced receipt and if found, ft will add an entry to Bon_Referenzen. This also applies if you want to void a previous receipt. See description of `BON_STORNO` above.
 
-If there are external references (from other systems or other cashpoints) to be added, then they can (optionally) be added as shown below:
+For a recommendation on how to connect the single requests via `cbReceiptReference` and `cbPreviousReceiptReference` see our Business Cases Examples document [here](https://fiskaltrust.de/wp-content/uploads/sites/5/2020/02/fiskaltrust-Business-Cases-in-JSON_englisch.pdf). 
+
+If you want (optional) to add other, additional references (from other systems or other cashpoints), you can add them by providing their data as shown below:
 
 | **Fieldname**            | **Description**          | **Format**          | **ft.input** |
 |----------------------|--------------------------|---------------------|---------------------|
@@ -514,11 +516,11 @@ If there are external references (from other systems or other cashpoints) to be
 | `BON_ID` | Action-ID | String (50) | `cbReceiptReference` |
 | `POS_ZEILE` | Line number of the referencing operation | String (50) | Automatically filled by ft  |
 | `REF_TYP` | Type of reference | "ExterneRechnung" or "ExternerLieferschein" or "Transaktion" or "ExterneSonstige" | can be sent via `ftReceiptCaseData` in JSON format. To send, add the key value pair `RefType ` e.g. `"ftReceiptCaseData":"{ ..., "RefType":"Transaktion", ... }"`. The value "Transaktion" mapps to an internal reference within this DSFinV-K export, all other values map to external references.|
-| `REF_NAME` | Description for type | String (40) | Mandatory if `RefType` is "ExterneSonstige", otherwise optional. Can be sent via `ftReceiptCaseData` in JSON format. To send, add the key value pair `RefName ` e.g. `"ftReceiptCaseData":"{ ..., "RefName":"Sonstige Sonderwurst", ... }"`.|
-| `REF_DATUM` | Date of the cashpoint closing | String (30) | mandatory if `RefType` is "Transaktion", otherwise optional. Can be sent via `ftReceiptCaseData` in JSON format. To send, add the key value pair `RefMoment` e.g. `"ftReceiptCaseData":"{ ..., "RefMoment":"2020-01-03T17:00:01", ... }"`.|
-| `REF_Z_KASSE_ID` | ID of the (closing) cashpoint | String (50) | Mandatory if `RefType` is "Transaktion", otherwise optional. Can be sent via `ftReceiptCaseData` in JSON format. To send, add the key value pair `RefCashBoxIdentification ` e.g. `"ftReceiptCaseData":"{ ..., "RefCashBoxIdentification":"AHHAH1919919", ... }"`.|
-| `REF_Z_NR` | No. of the cashpoint closing | Integer | Mandatory if `RefType` is "Transaktion", otherwise optional. Can be sent via `ftReceiptCaseData` in JSON format. To send, add the key value pair `RefClosingNr` e.g. `"ftReceiptCaseData":"{ ..., "RefClosingNr":1091029, ... }"`. (tbd: if ft generates the closing nr., than how do I receive it as a caller?) |
-| `REF_BON_ID` | Action-ID | String (40) | mandatory, can be sent via `ftReceiptCaseData` in JSON format. To send, add the key value pair `RefReceiptId` e.g. `"ftReceiptCaseData":"{ ..., "RefReceiptId":"UAUUA1112", ... }"`.|
+| `REF_NAME` | Description for type | String (40) | If the external reference you want to add is of type (`RefType`) "ExterneSonstige", you must provide data for the field `REF_NAME`. Please send it via `ftReceiptCaseData` in JSON format.by adding the key value pair `RefName ` e.g. `"ftReceiptCaseData":"{ ..., "RefName":"Sonstige Sonderwurst", ... }"`.|
+| `REF_DATUM` | Date of the cashpoint closing | String (30) | If the reference you want to add refers to another cashpoint and therefore is of type (`RefType`) "Transaktion", you must provide data for the field `REF_DATUM`. Please send it via `ftReceiptCaseData` in JSON format by adding the key value pair `RefMoment` e.g. `"ftReceiptCaseData":"{ ..., "RefMoment":"2020-01-03T17:00:01", ... }"`.|
+| `REF_Z_KASSE_ID` | ID of the (closing) cashpoint | String (50) | If the reference you want to add refers to another cashpoint and therefore is of type (`RefType`) "Transaktion", you must provide data for the field `REF_Z_KASSE_ID`. Please send it via `ftReceiptCaseData` in JSON format by adding the key value pair `RefCashBoxIdentification ` e.g. `"ftReceiptCaseData":"{ ..., "RefCashBoxIdentification":"AHHAH1919919", ... }"`.|
+| `REF_Z_NR` | No. of the cashpoint closing | Integer | If the reference you want to add refers to another cashpoint and therefore is of type (`RefType`) "Transaktion", you must provide data for the field `REF_Z_NR`. Please sent it via `ftReceiptCaseData` in JSON formatby adding the key value pair `RefClosingNr` e.g. `"ftReceiptCaseData":"{ ..., "RefClosingNr":1091029, ... }"`. (tbd: if ft generates the closing nr., than how do I receive it as a caller?) |
+| `REF_BON_ID` | Action-ID | String (40) | If the reference you want to add refers to another cashpoint and therefore is of type (`RefType`) "Transaktion", you must provide data for the field `REF_BON_ID`. Please sent it via `ftReceiptCaseData` in JSON formatby adding the key value pair `RefReceiptId` e.g. `"ftReceiptCaseData":"{ ..., "RefReceiptId":"UAUUA1112#20200211-112430", ... }"`.|
 
 ##### File: TSE_Transaktionen (transactions_tse.csv)