-
Notifications
You must be signed in to change notification settings - Fork 186
Expand file tree
/
Copy pathbatchCIE.go
More file actions
135 lines (121 loc) · 4.62 KB
/
batchCIE.go
File metadata and controls
135 lines (121 loc) · 4.62 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
// Licensed to The Moov Authors under one or more contributor
// license agreements. See the NOTICE file distributed with
// this work for additional information regarding copyright
// ownership. The Moov Authors licenses this file to you under
// the Apache License, Version 2.0 (the "License"); you may
// not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing,
// software distributed under the License is distributed on an
// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
// KIND, either express or implied. See the License for the
// specific language governing permissions and limitations
// under the License.
package ach
// BatchCIE holds the BatchHeader and BatchControl and all EntryDetail for CIE Entries.
//
// Customer-Initiated Entry (or CIE entry) is a credit entry initiated on behalf of,
// and upon the instruction of, a consumer to transfer funds to a non-consumer Receiver.
// CIE entries are usually transmitted to a company for payment of funds that the consumer
// owes to that company and are initiated by the consumer through some type of online
// banking product or bill payment service provider. With CIEs, funds owed by the consumer
// are “pushed” to the biller in the form of an ACH credit, as opposed to the biller's use of
// a debit application (e.g., PPD, WEB) to “pull” the funds from a customer's account.
type BatchCIE struct {
Batch
}
// NewBatchCIE returns a *BatchCIE
func NewBatchCIE(bh *BatchHeader) *BatchCIE {
batch := new(BatchCIE)
batch.SetControl(NewBatchControl())
batch.SetHeader(bh)
batch.SetID(bh.ID)
return batch
}
// Validate checks properties of the ACH batch to ensure they match NACHA guidelines.
// This includes computing checksums, totals, and sequence orderings.
//
// Validate will never modify the batch.
func (batch *BatchCIE) Validate() error {
if batch.validateOpts != nil && (batch.validateOpts.SkipAll || batch.validateOpts.BypassBatchValidation) {
return nil
}
// basic verification of the batch before we validate specific rules.
if err := batch.verify(); err != nil {
return err
}
// Add configuration based validation for this type.
// Add type specific validation.
if batch.Header.StandardEntryClassCode != CIE {
return batch.Error("StandardEntryClassCode", ErrBatchSECType, CIE)
}
// CIE detail entries can only be a credit, ServiceClassCode must allow credit
switch batch.Header.ServiceClassCode {
case DebitsOnly:
return batch.Error("ServiceClassCode", ErrBatchServiceClassCode, batch.Header.ServiceClassCode)
}
invalidEntries := batch.InvalidEntries()
if len(invalidEntries) > 0 {
return invalidEntries[0].Error // return the first invalid entry's error
}
return nil
}
// InvalidEntries returns entries with validation errors in the batch
func (batch *BatchCIE) InvalidEntries() []InvalidEntry {
var out []InvalidEntry
for _, entry := range batch.Entries {
// CIE detail entries must be a debit
if entry.CreditOrDebit() != "C" {
out = append(out, InvalidEntry{
Entry: entry,
Error: batch.Error("TransactionCode", ErrBatchDebitOnly, entry.TransactionCode),
})
}
// CIE must have a maximum of one Addenda05 record
if len(entry.Addenda05) > 1 {
out = append(out, InvalidEntry{
Entry: entry,
Error: batch.Error("AddendaCount", NewErrBatchAddendaCount(len(entry.Addenda05), 1)),
})
}
// Verify the Amount is valid for SEC code and TransactionCode
if err := batch.ValidAmountForCodes(entry); err != nil {
out = append(out, InvalidEntry{
Entry: entry,
Error: err,
})
}
// Verify the TransactionCode is valid for a ServiceClassCode
if err := batch.ValidTranCodeForServiceClassCode(entry); err != nil {
out = append(out, InvalidEntry{
Entry: entry,
Error: err,
})
}
// Verify Addenda* FieldInclusion based on entry.Category and batchHeader.StandardEntryClassCode
if err := batch.addendaFieldInclusion(entry); err != nil {
out = append(out, InvalidEntry{
Entry: entry,
Error: err,
})
}
}
return out
}
// Create will tabulate and assemble an ACH batch into a valid state. This includes
// setting any posting dates, sequence numbers, counts, and sums.
//
// Create implementations are free to modify computable fields in a file and should
// call the Batch's Validate function at the end of their execution.
func (batch *BatchCIE) Create() error {
// generates sequence numbers and batch control
if err := batch.build(); err != nil {
return err
}
// Additional steps specific to batch type
// ...
return batch.Validate()
}