| Syntax Notes |
| 07 | P0708 - If either DAD07 or DAD08 is present, then the other is required. |
| 10 | C1009 - If DAD10 is present, then DAD09 is required. |
| 11 | P1112 - If either DAD11 or DAD12 is present, then the other is required. |
| Semantic Notes |
| 03 | DAD03 identifies the date on or after which a debit can be posted to the account identified in the BAU segment. |
| 04 | DAD04 identifies the last date that the debit can be applied, if used. |
| 09 | If DAD09 and DAD10 are present, they represent the beginning and end of a range of numbers. If only DAD09 is used, it represents a single reference (i.e., not the beginning of a range). DAD09 and DAD10, if used must contain values that are known to the originator of the debit authorization. For check issuance, DAD09 and DAD10 contain the range of check numbers. In the case of ACH debits, the value shall coincide with the content of the Individual ID of the NACHA Detail (Type 6) record. |
| 14 | DAD14 is the count of days. |
| Comments |
| 00 | Every DAD shall be unique. |
| 01 | When DAD01 contains a "3" (for deletion), this DAD must have the same information as the DAD being deleted. |
| 04 | DAD04 must contain a value that is later than or equal to the value of DAD03, if used. |
| 05 | This element is only applicable in an ACH environment. If used, DAD05 shall contain a value that is known to the originator of the debit authorization and will be carried in the ACH debit transaction. This value should coincide with the content of the company ID of the NACHA Batch Header (Type 5) record. |
| 11 | DAD11 through DAD13 provide information regarding the party initiating the debit, if used. (This is unlike the BAU03 through BAU05 which applies to the party affected by the debit.) |
| 14 | DAD14 should be used only if this is a recurring debit (DAD07 equals "R"). |
| 15 | DAD15 should be used only if this is a recurring debit (DAD07 equals "R"). |