-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Sprint 26 Changes: Issue #478 Add Meta Description for Smart Bulletin No. 033 - "Prohibited Vendors" Issue #474 Footer Changes for SmartPay Program Website Issue #145 Individual Smart Bulletins as HTML Pages Issue #470 Convert Smart Bulletins from PDF to HTML (Smart Bulletins #17 - # 21 and #23 - #28) Issue #472 Convert Smart Bulletins from PDF to HTML (Smart Bulletins #1 - # 16)
- Loading branch information
Showing
40 changed files
with
1,631 additions
and
221 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
--- | ||
title: "Smart Bulletin No. 001" | ||
intro: "Introduction to GSA SmartPay® Smart Bulletins" | ||
number: "No. 001" | ||
order: 001 | ||
businessline: "Purchase, Travel, Fleet, and Integrated" | ||
published: "Jan 18, 2007" | ||
lastupdated: "Mar 22, 2024" | ||
--- | ||
|
||
UPDATE: | ||
| Date | Version History Action Log - Summary of Action/Changes | | ||
| ----------- | ----------- | | ||
| January 18, 2007 | Implementation of Smart Bulletin #01 | | ||
| March 22, 2024 | Revised for administrative updates | | ||
|
||
## Effective Date | ||
|
||
From Issuance until superseded | ||
|
||
|
||
## Business Line(s) Affected | ||
|
||
A statement of which GSA SmartPay business line(s) (Purchase, Travel, Fleet, Integrated) will be affected by the new or updated policy, regulation, or law. | ||
|
||
## Summary | ||
|
||
The GSA SmartPay Program Office has initiated the GSA SmartPay Smart Bulletins to keep customer agencies and stakeholders informed of new or updated policies, regulations, charge card management practices, task order administration information, master contract changes, and laws relevant to government charge cards. These bulletins are intended to be a source of other information, providing operational guidance to GSA SmartPay customers. These are not intended to be policy issuances. | ||
|
||
GSA SmartPay Smart Bulletins will be structured as follows: | ||
|
||
- **Introduction** – An explanation of the purpose of the GSA SmartPay Smart Bulletin, which will include relevant information such as the issuer of the new or updated policy, regulation, or law and the reason for the change. | ||
- **Business Line(s) Affected** – A statement of which GSA SmartPay business line(s) (Purchase, Travel, Fleet, Integrated) will be affected by the new or updated policy, regulation, or law. | ||
- **Summary** – A brief summary of the new or updated policy, regulation, or law. | ||
- **Effect of Policy Change** – Effect of the new or updated policy, regulation, or law ___on GSA SmartPay customers. | ||
- **Action** – Action to take as a result of, or to be in compliance with, the new or updated policy, regulation, or law. | ||
- **Timeframe** – Period of time the new or updated policy, regulation, information, or law is effective/relevant. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
--- | ||
title: "Smart Bulletin No. 002" | ||
intro: "FAR Amendment: Micro-purchase threshold limit increased to $10,000" | ||
number: "No. 002" | ||
order: 002 | ||
businessline: "Purchase and Integrated" | ||
published: "Jan 18, 2007" | ||
lastupdated: "Mar 22, 2024" | ||
--- | ||
|
||
UPDATE: | ||
| Date | Version History Action Log - Summary of Action/Changes | | ||
| ----------- | ----------- | | ||
| January 18, 2007 | Implementation of Smart Bulletin #02 | | ||
| November 14, 2023 | Re-written to reflect current information for the micro-purchase threshold, in accordance with the Federal Acquisition Regulation and applicable United States Code. | | ||
| March 22, 2024 | Revised for administrative updates | | ||
|
||
## Effective Date | ||
|
||
From Issuance until superseded | ||
|
||
|
||
## Business Line(s) Affected | ||
|
||
Purchase, and Integrated | ||
|
||
|
||
## Introduction | ||
|
||
In accordance with the [Federal Acquisition Regulation (FAR) Subpart 13.2 - Actions At or Below the Micro-Purchase Threshold](https://www.acquisition.gov/far/subpart-13.2), “The Government wide commercial purchase card shall be the preferred method to purchase and to pay for micro-purchases.” The purpose of this GSA SmartPay® Smart Bulletin is to provide information to charge card managers, cardholders, and stakeholders about the government micro-purchase threshold. | ||
|
||
|
||
## Definition | ||
|
||
In accordance with [FAR 2.101 Definitions](https://www.acquisition.gov/far/subpart-2.1#FAR_2_101), a “Micro-purchase means an acquisition of supplies or services using simplified acquisition procedures, the aggregate amount of which does not exceed the micro-purchase threshold.” The micro-purchase threshold limit is established in [FAR 2.101 Definitions](https://www.acquisition.gov/far/subpart-2.1#FAR_2_101). Convenience checks may not be issued for an amount in excess of one half of the micro-purchase threshold under [41 U.S.C. chapter 12, Simplified Acquisition Procedures](https://uscode.house.gov/view.xhtml?path=/prelim@title41/subtitle1/divisionB/chapter19&edition=prelim). | ||
|
||
|
||
## Exceptions | ||
|
||
[FAR 2.101 Definitions](https://www.acquisition.gov/far/subpart-2.1#FAR_2_101) establishes the micro-purchase threshold limit. However there are exceptions to this limit, which are each defined and the threshold is established in the definition of micro-purchase threshold in [FAR 2.101 Definitions](https://www.acquisition.gov/far/subpart-2.1#FAR_2_101). These include the following: | ||
|
||
- **Construction:** Defined under construction and subject to [40 U.S.C. chapter 31, subchapter IV, Wage Rate Requirements](https://uscode.house.gov/view.xhtml?path=/prelim@title40/subtitle2/partA/chapter31/subchapter4&edition=prelim). | ||
- **Services:** Subject to [41 U.S.C. chapter 67, Service Contract Labor Standards](https://uscode.house.gov/view.xhtml?path=/prelim@title41/subtitle2/chapter67&edition=prelim). | ||
- **Contingency Operations:** Defined under contingency operations and [10 U.S.C. 101, Definitions](https://uscode.house.gov/view.xhtml?req=(title:10%20section:101%20edition:prelim)%20OR%20(granuleid:USC-prelim-title10-section101)&f=treesort&edition=prelim&num=0&jumpTo=true). Please see [FAR 2.101 Definitions](https://www.acquisition.gov/far/subpart-2.1#FAR_2_101) for micro-purchase limits for purchases within the United States and purchases made outside of the United States. | ||
- **Higher Education:** Acquisitions of supplies or services from institutions of higher education or related or affiliated nonprofit entities, or from nonprofit research organizations or independent research institutes. | ||
|
||
|
||
## Action | ||
Agencies are not required to designate purchase limits at the maximum micro-purchase limits established by the FAR. Instead, agencies should consider evaluating current procurement needs, established spending controls, and current purchase card spending limits to determine whether or setting spending limits at the micro-purchase threshold is required to meet the needs of an agency. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
--- | ||
title: "Smart Bulletin No. 003" | ||
intro: "Phone Fraud Scams" | ||
number: "No. 003" | ||
order: 003 | ||
businessline: "Purchase, Travel, Fleet, and Integrated" | ||
published: "Mar 9, 2007" | ||
lastupdated: "Mar 22, 2024" | ||
--- | ||
|
||
<div | ||
class="usa-alert margin-y-2 usa-alert--warning" | ||
data-test="alert-container" | ||
> | ||
<div class="usa-alert__body"> | ||
<p | ||
class="usa-alert__text" | ||
> | ||
This Smart Bulletin was Archived on July 6, 2023 | ||
</p> | ||
</div> | ||
</div> | ||
|
||
UPDATE: | ||
| Date | Version History Action Log - Summary of Action/Changes | | ||
| ----------- | ----------- | | ||
| March 9, 2007 | Implementation of Smart Bulletin #03 | | ||
| July 6, 2023 | Archived | | ||
| March 22, 2024 | Revised for administrative updates | | ||
|
||
## Effective Date | ||
|
||
From Issuance through July 6, 2023 | ||
|
||
|
||
## Business Line(s) Affected | ||
|
||
Purchase, Travel, Fleet, and Integrated | ||
|
||
|
||
## Introduction | ||
|
||
The purpose of this GSA SmartPay Smart Bulletin is to inform customer agencies of a new type of phone fraud scam involving the Card Verification Value 2 (CVV2) code on the back of charge cards. Although this office cannot confirm any specific incidents of this particular scam involving government cardholders, VISA has confirmed that similar scams exist. | ||
|
||
|
||
## Summary | ||
|
||
The GSA SmartPay Office has been made aware of a new type of phone fraud scam in which criminals who already possess personal information such as names, account numbers, and addresses ask you to verify the 3-digit Card Verification Value 2(CVV2) code on the back of your card. The CVV2 code is often asked for by merchants so that they can secure "card not present" transactions occurring over the Internet, by mail, fax, or over the phone. In many cases, the cardholder is fooled into a false sense of security by the criminal (generally posing as a bank “fraud investigator”) revealing a portion of the cardholder’s personally identifiable information before asking them to “verify” the CVV2 code on the back of their card. | ||
|
||
|
||
## Action | ||
Cardholders should be aware that banks or associations will never ask for personal information via phone or email unless the call was initiated by the cardholder. Never reveal any personal information when solicited via phone or email. Instead, if unsure, contact the bank or association directly using a phone number or email address you know is valid, to confirm that you are speaking with an authorized employee. Never use any phone numbers or hyperlinks provided to you in unsolicited phone calls or emails. Instead, use the phone numbers provided on the back of your card, or manually enter a | ||
url that you know to be official into a separate browser (i.e. close the website in question and re-open a web browser such as Internet Explorer, Netscape, or Firefox to enter a url address that you know to be authentic). | ||
|
||
For more information on how to protect yourself against common scams, fraud, and identity theft, please visit the following association links: | ||
|
||
https://usa.visa.com/support/consumer/security.html | ||
|
||
https://sea.mastercard.com/en-region-sea/business/merchants/safety-and-security/suspect-fraud.html |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
--- | ||
title: "Smart Bulletin No. 004" | ||
intro: "Notice Regarding Prohibition of Signing Bonuses and Lump Sum Incentives for Task Orders Awarded Under GSA SmartPay® 3" | ||
number: "No. 004" | ||
order: 004 | ||
businessline: "Purchase, Travel, Fleet, and Integrated" | ||
published: "May 31, 2018" | ||
lastupdated: "Mar 22, 2024" | ||
--- | ||
|
||
UPDATE: | ||
| Date | Version History Action Log - Summary of Action/Changes | | ||
| ----------- | ----------- | | ||
| May 31, 2018 | Implementation of Smart Bulletin #04 | | ||
| July 13, 2023 | Revised for administrative format change(s) | | ||
| March 22, 2024 | Revised for administrative updates | | ||
|
||
## Effective Date | ||
|
||
From Issuance until superseded | ||
|
||
|
||
## Business Line(s) Affected | ||
|
||
Purchase, Travel, Fleet, and Integrated | ||
|
||
|
||
## Introduction | ||
|
||
The purpose of this GSA SmartPay Policy Bulletin is to inform customer agencies and stakeholders that agencies/organizations that will award task orders under the SP3 Master Contracts are not permitted to accept signing bonuses or lump sum incentives from SP3 contractors when awarding task orders, absent agency unique authority to the contrary. | ||
|
||
|
||
## Summary | ||
|
||
In general, pursuant to 31 U.S.C. § 3302 and absent specific statutory authority, all funds received for the use of the United States must be deposited in the general fund of the Treasury to the credit of the appropriate account, unless deposit credit of an appropriation or other fund account is authorized by law. Violation of this statute is an illegal "augmentation" of the appropriation, and funds must be returned to the Treasury and are appropriated by Congress. | ||
|
||
An exception to this general rule is that an agency may retain receipts that qualify as "refunds." Refunds are defined as "repayments for excess payments" and are to be credited to the appropriation or fund accounts from which the excess payments were made, absent agency authority to the contrary. Refunds are also defined as representing "amounts collected from outside sources for payments made in error, overpayments, or adjustments for previous amounts disbursed." See Rebates from Travel Management Center Contractors, B- 217913, 65 Comp. Gen. 600; May 30, 1986; Accounting for Rebates from Travel Management Center Contractors, B-217913.3, 73 Comp. Gen. 210, June 24, 1994. Refunds must be directly related to previously recorded expenditures and are reductions of such expenditures. A lump sum incentive or signing bonus does not fit within the category of payments that may be retained and any such payment must be credited to the general fund of the Treasury. A lump sum incentive or signing bonus under an SP3 task order award would be a payment made at the beginning of the performance period and would not be tied to actual expenditures and use of the charge cards. Thus, it cannot be considered a reimbursement, advance or funds, refund or recovery. | ||
|
||
|
||
## Resources | ||
|
||
If an agency/organization is offered a lump sum incentive or signing bonus by a SP3 contractor, they should contact their GSA SmartPay representative immediately with a detailed account of the occurrence. Some agencies/organizations may have unique authorities which may permit them to retain signing bonuses or other lump sum incentives. In such cases, charge card management officials are asked to coordinate with the agencies/organizations legal and financial staff to confirm the proper handling of these funds. | ||
|
||
## Action |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
--- | ||
title: "Smart Bulletin No. 005" | ||
intro: "Notice Regarding Transaction Dispute Time Frame under GSA SmartPay® Master Contract" | ||
number: "No. 005" | ||
order: 005 | ||
businessline: "Purchase, Travel, Fleet, and Integrated" | ||
published: "Oct 31, 2008" | ||
lastupdated: "Mar 22, 2024" | ||
--- | ||
|
||
UPDATE: | ||
| Date | Version History Action Log - Summary of Action/Changes | | ||
| ----------- | ----------- | | ||
| October 31, 2008 | Implementation of Smart Bulletin #05 | | ||
| July 26, 2023 | Revised to update to GSA SmartPay 3 Master Contract language and remove obsolete guidance. | | ||
| March 22, 2024 | Revised for administrative updates | | ||
|
||
## Effective Date | ||
|
||
From Issuance until superseded | ||
|
||
|
||
## Business Line(s) Affected | ||
|
||
Purchase, Travel, Fleet, and Integrated | ||
|
||
|
||
## Introduction | ||
|
||
The GSA SmartPay master contract provides 90 calendar days following the transaction date to file a dispute. It is highly recommended not to delay filing a dispute when required. | ||
|
||
|
||
## Summary | ||
|
||
According to GSA SmartPay 3 master contract Section C.3.3.14.1, “the invoice will be electronically reconciled by the agency/organization or designee, unless otherwise specified at the task order level. The account holder is responsible for notifying the Contractor of any items in dispute and shall have 90 calendar days from the transaction date to initiate a dispute, unless otherwise specified by the agency/organization. This notification of transaction dispute may occur via the electronic access system described in C.7.1 Electronic Access System, by telephone, or other electronic means (e.g., email). If a disputed item is resolved before the payment due date, the resolution shall appear on the agency’s/organization’s invoice for the next billing cycle.” | ||
|
||
|
||
## Action | ||
|
||
Cardholders should regularly access their accounts through their servicing contractor bank’s electronic access system, verifying the charges on the account on a regular basis. As soon as a dispute is deemed necessary, cardholders should not delay in notifying the contractor bank. Submitting a dispute as early as possible will ensure the contractor bank has ample time to investigate the disputed transaction. Allowing the maximum time for investigation will give the cardholder the best chance for thorough dispute investigation and afford the bank contractor the best opportunity to charge back the merchant if necessary. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
--- | ||
title: "Smart Bulletin No. 006" | ||
intro: "GSA SmartPay® Master Contract Record-Keeping Requirements" | ||
number: "No. 006" | ||
order: 006 | ||
businessline: "Purchase, Travel, Fleet, and Integrated" | ||
published: "" | ||
lastupdated: "Nov 30, 2008" | ||
--- | ||
|
||
UPDATE: | ||
| Date | Version History Action Log - Summary of Action/Changes | | ||
| ----------- | ----------- | | ||
| November 30, 2008 | Implementation of Smart Bulletin #06 | | ||
| August 8, 2023 | Revised for administrative format change(s), updated to reflect GSA SmartPay 3 Master Contract references. | | ||
| March 22, 2024 | Revised for administrative updates | | ||
|
||
## Effective Date | ||
|
||
From Issuance until superseded | ||
|
||
|
||
## Business Line(s) Affected | ||
|
||
Purchase, Travel, Fleet and Integrated | ||
|
||
|
||
## Introduction | ||
|
||
The purpose of this GSA SmartPay Smart Bulletin is to inform customer agencies of the contractors’ record retention and reporting requirements under the GSA SmartPay 3 Master Contract. | ||
|
||
|
||
## Summary | ||
|
||
The GSA SmartPay 3 Master Contract includes the following clauses: | ||
|
||
>### C.7.2.4 Record Retention and Retrieval | ||
>In addition to the record retention requirements of FAR Part 4.703 Contractor Records Retention, the Contractor shall serve as the document repository agent for all GSA SmartPay transactions. The Contractor shall maintain electronic records of all transactions for a period of six (6) years after final contract payment. Final contract payment is defined as the final payment for the particular charge under each agency’s/organization’s task order. If the Contractor elects to add new file formats, then the Contractor shall provide a proposal to the GSA Contracting Officer that identifies the new file format and a schedule for implementation. The GSA Contracting Officer will have 30 calendar days to review and approve/disapprove the proposal. Any new file formats will be incorporated by contract modification. | ||
>### C.7.3 Reporting Requirements | ||
>GSA and agencies/organizations may choose to receive some or all of the following reports | ||
and shall determine the frequency, distribution points, and method of transmission at the task order level. The agency/organization may develop performance objectives to assess Contractor compliance with agency/organization reporting requirements at the task order level. For each performance objective, the agency/organization may specify performance standards, acceptable quality level, and a method of assessment. Examples of performance objectives for reporting include but are not limited to, timeliness and accuracy of the reports. The Contractor shall provide the ability for GSA and/or agencies/organizations to create ad-hoc reports based on program and transaction data elements. Reports shall include the ability to roll-up or break down the reports by agency/organization levels within an agency/organization (e.g., department, major components within a department, offices within major components, sub-elements within offices) and summary levels. The Contractor shall offer standard commercial reports. If the Contractor has a commercial report that will meet the stated specific need, it may propose that report as an alternative and the GSA COR shall decide if the alternative may be substituted, if demonstrated to meet the requirements. | ||
Transmission of all reports is required through the EAS (see C.7.1 Electronic Access System), unless otherwise specified by the agency/organization at the task order level. At a minimum, the reports shall correspond with the agency/organization billing cycle. The Contractor shall offer alternative electronic reporting cycles (including, but not limited to, daily, weekly, monthly) to meet agency/organization specific requirements. The Contractor shall provide data separated by transaction type (i.e., Purchase, Travel, Fleet) for reporting purposes, unless otherwise specified by GSA and/or the agency/organization. Release of program and transaction data is governed by 5 U.S.C. § 552, Freedom of Information Act (FOIA) in most instances. Reports shall be, in accordance with agency/organization FOIA compliance procedures. | ||
|
||
|
||
## Action | ||
|
||
Agencies should educate their card program managers on record retention and reporting requirements. It is important to keep accounts up to date throughout the contract period of performance so that the agency is in a good position to avoid contract close-out issues at the end of the GSA SmartPay Master Contract. |
Oops, something went wrong.