6509.17,30
Page 1 of 3
FOREST SERVICE HANDBOOK
Portland, Oregon
FSH 6509.17 - AUTOMATED TIMBER SALE ACCOUNTING HANDBOOK
R-6 Supplement No. 6509.17-92-3
Effective October 5, 1992
POSTING NOTICE. Supplements to this handbook are numbered consecutively.
Check the last transmittal sheet received for this handbook to see that the above
supplement number is in sequence. If not, obtain intervening supplement(s) at once
from the Information Center. Do not post this supplement until the missing one(s)
is received and posted. After posting, place the transmittal at the front of the title
and retain until the first transmittal of the next calendar year is received.
The last R-6 Supplement to this handbook was 6509.17-92-2. (10.2-14.32)
Document Name
6509.17,30
Digest:
Finalizes Region 6 ATSA chapter previously in draft.
/s/ John E. Lowe
JOHN E. LOWE
Regional Forester
Superseded New
(Number of Sheets)
3
R6 SUPPLEMENT 6509.17-92-3
EFFECTIVE 10/05/92
6509.17,30
Page 2 of 3
FSH 6509.17 - AUTOMATED TIMBER SALE ACCOUNTING HANDBOOK
R-6 SUPPLEMENT 6509.17-92-3
EFFECTIVE 10/05/92
CHAPTER 30 - NEW AGREEMENTS INPUT TRANSACTIONS,
MODIFICATIONS AND DELETIONS OF AGREEMENTS DATA
31 - AGREEMENTS SUBSYSTEM. Bond filing and retention is described in FSH
6509.11k Service-Wide Finance and Accounting Handbook Chapter 80. Generally,
file single bonds within the timber sale contract folder and retain in accordance
with FSH 6209.11 Records Management Handbook. An exception may be original
Letters-of-Credit filed in a secured area. In this instance, a copy should be placed
and retained in the timber sale contract folder. Blanket payment bonds should be
kept in a separate file but must cross-reference related files. Retain blanket bonds
for the same period equal to the retention of the last timber sale covered by the
bond. Keep and retain all written requests for allocation of the blanket bond under
B/BT 4.31 by the purchaser as timber sale contract documents in accordance with
FSH 6209.11.
31.13 - Performance Bond as Security for Felled Timber (Coverage Code 3).
Currently Forests must carefully monitor tree measurement sales that contain
CT4.228. The provision is for timber cut but not removed. On tree measurement
contracts which contain this provision, the ATSA system is incorrectly using the
Performance Bond to cover the value of timber cut and removed.
31.22 - Blanket. The parent text states that "a performance bond that is used to
guarantee contract performance and as security for material cut, but not removed
from the sale area, is coded as a blanket bond even though it applies to only one
sale." Forests, at their option, may code these as a single agreement with a
coverage type (field 68) 3.
32 - AGREEMENT TRANSACTIONS.
32.1 - 3001 Transaction - Basic Agreement Data (Form FS-6500-195).
32.11d - Document Date. On a blanket agreement 3001 M transaction, the
document date cannot be modified to a date later than the earliest sale allocation
date.
32.11e - Expiration Date. At this time the ATSA system will not accept an
Agreement Expiration Date which is in the year 2000. Enter the agreement with
an expiration date of 12/31/99. After the ATSA program change, a query against
this agreement expiration date will be made to identify agreements which may need
modification.
R6 SUPPLEMENT 6509.17-92-3
EFFECTIVE 10/05/92
6509.17,30
Page 3 of 3
32.3 - 3101 Transaction - Agreement Individual Contract Release Date (Form FS6500-196). If the current allocation to the agreement is zero, the ATSA system will
allow a timber sale contract to be closed without removing the agreement
information from the agreement subsystem. In this case a 3101 release transaction
will result in the error message "Contract does not exist." To delete a contract from
a blanket agreement, submit a 3201 D transaction leaving fields 30-44 blank.
Always release single agreements using a 3101 transaction prior to sale closure
rather than setting their allocation to zero using a 3001 M transaction.
32.31f - Release Date. When a release date is entered on a 3101 M transaction, the
ATSA system automatically sets the allocation amount to zero, and the allocation
date is removed. The ATSA system automatically removes it from the agreement
subsystem at the end of the quarter. New allocations will not be allowed until the
release date has been deleted using 3101 D transaction. Previously entered release
dates may be deleted provided the contract is still present on the agreements
master file and the contracts data base. A 3101 D transaction removes the release
date, and on single agreements re-allocates the dollar amount. On blanket
agreements, only the release date is removed and the allocation is set to zero.
32.4 - 3201 Transaction - Agreement Individual Contract Allocation (Form FS-6500197).
32.44f - Allocation Date. The ATSA system does not allow an allocation date earlier
than the current agreement document date or later than the current agreement
expiration date.