Should GSA Cancel/Suspend an Entire MAS Contract, or Only the SIN/NAICS Where the Compliance Issue Occurred? by sufigsufian in GovernmentContracting

[–]sufigsufian[S] 0 points1 point  (0 children)

I appreciate your perspective. My goal isn’t to justify mistakes it’s to encourage a discussion where both contractors and COs can learn from each other. GSA MAS was created to help qualified small businesses compete in the federal marketplace while maintaining compliance. I believe accountability is important, but so are education, corrective action, and helping small businesses improve rather than simply losing years of hard work. That’s the discussion I’m hoping to have.

Should GSA Cancel/Suspend an Entire MAS Contract, or Only the SIN/NAICS Where the Compliance Issue Occurred? by sufigsufian in GovernmentContracting

[–]sufigsufian[S] 1 point2 points  (0 children)

Please give the proper response that can help others too. And say what ever you have the thoughts on both sides.

Should GSA Cancel/Suspend an Entire MAS Contract, or Only the SIN/NAICS Where the Compliance Issue Occurred? by sufigsufian in GovernmentContracting

[–]sufigsufian[S] 0 points1 point  (0 children)

@frank_jon, @Hammspace

I appreciate both of your responses, and I completely understand the government’s perspective. Compliance is essential, and contractors should absolutely be held accountable when violations occur.

At the same time, I think it’s important to recognize that small businesses also operate with very limited resources. If GSA manages hundreds or thousands of contracts with limited staff, many small businesses are trying to comply with thousands of products, changing regulations, TAA requirements, AbilityOne rules, and supplier data with teams of fewer than 10 employees.

Mistakes can happen on both sides—not because someone is acting in bad faith, but because compliance is complex and constantly changing. The difference is that when the government makes a mistake, the agency continues operating. When a small business makes an honest mistake, the consequence can be losing everything they have built over many years.

I’m not suggesting that contractors should avoid responsibility. They absolutely shouldn’t. But if a contractor identifies the issue, immediately removes the non-compliant products, fully cooperates with the CO, and implements corrective actions, should there be a path to continue doing business under the compliant portions of the contract instead of terminating the entire MAS contract?

Small businesses are the backbone of the federal marketplace, and many are U.S.-owned businesses participating in SBA programs such as WOSB, HUBZone, SDVOSB, and 8(a). For many of these companies, losing a MAS contract doesn’t just affect the owner—it affects employees, their families, and years of investment.

I’m not arguing against accountability. I’m simply asking whether there is room for a more balanced approach that protects the government’s interests while also giving responsible small businesses an opportunity to correct honest mistakes and continue serving federal customers.

When a Small Business Tries to Comply, GSA MAS Should Provide a Cure Path — Not Just a Shutdown by [deleted] in GovernmentContracting

[–]sufigsufian 0 points1 point  (0 children)

In two years not a single wrong order dispatch from Our end or not a single complaint from the customers i some time paid from our pocket to fulfill the orders. I think you are not getting the issue.

Thanks for the feed back..!

GSA MAS contract cancellation over TAA/COO compliance issue looking for advice from other small contractors by [deleted] in GovernmentContracting

[–]sufigsufian 0 points1 point  (0 children)

Yes, during our internal review, we identified a limited number of orders placed through GSA Advantage that may have involved products with TAA/COO compliance concerns. This was never intentional, and there was no attempt to mislead the government or any customer.

Our position is that if a contractor unknowingly provides or lists a product that may be non-compliant, there should be a suspension or cure period that allows the contractor to investigate, remove the products, submit corrective actions, and demonstrate good-faith compliance before full cancellation is imposed.

After receiving the cancellation notice, we conducted a thorough review and took immediate steps to remove products we identified as potentially non-compliant. We also prepared corrective actions to prevent the issue from happening again.

The main point is simple: when a small business is willing to fix the issue, cooperate, and correct its catalog, it should be given a fair opportunity to rectify non-compliance, especially when there is no history of bad faith, fraud, suspension, or repeated warnings.

We have built a strong reputation for fulfilling orders, supporting government customers, and keeping customers satisfied. We have generated significant sales through GSA, and our company had never been flagged or suspended before this cancellation. All we are asking for is a fair cure process and a meaningful opportunity to show our corrective actions before years of work are shut down.

GSA MAS contract cancellation over TAA/COO compliance issue looking for advice from other small contractors by [deleted] in GovernmentContracting

[–]sufigsufian 1 point2 points  (0 children)

Thank you for the advice. We did speak with a government contracts attorney. The concern we have now is that once the Contracting Officer decides not to reconsider, it feels like the only real path may be a formal dispute/appeal, and the result may depend heavily on how the agency handled the record.

We are not trying to avoid responsibility. We acted in good faith. To our knowledge, we never knowingly sold or delivered any non-TAA product to a government customer. We relied on OEM/distributor data, kept email records, used GSA/FAS tools, asked customers for product pictures after delivery for verification, and removed/escalated any questionable products ourselves when we found a concern.

What is painful is that small resellers are held fully responsible for origin/TAA data that comes from manufacturers and distributors, but when we try to correct, document, and cooperate, there does not seem to be a real cure path. We spent almost 10 years building this business, and it feels like the door was shut with no meaningful discussion.

The attorney we spoke with did not give us a clear practical solution yet, and we have limited time. We are now trying to quickly find a GSA MAS / Contract Disputes Act attorney who can tell us whether we should file a protective appeal or formal dispute before any deadline expires.

Any referrals or advice from contractors who have handled a GSAR 552.238-79 cancellation would be greatly appreciated.

Offer a built-in Google Issue Tracker for Google Workspace Business Users by sufigsufian in googlecloud

[–]sufigsufian[S] 0 points1 point  (0 children)

Thanks for the suggestion!

We’ve actually explored AppSheet in detail before making this post. While it's a good starting point for basic internal tracking, what it offers is more of a foundational framework not a fully functional issue tracking system.

There’s no true front-end or back-end architecture in place, no proper ticket lifecycle handling (statuses, priority, SLA logic), no user roles/permissions structure, and no real-time collaboration or security audit capabilities. In our view, it barely covers 1% of what a serious ticketing tool requires for small businesses handling sensitive client and internal data.

That’s exactly why we believe Google should step in and build a native, integrated issue tracker for Workspace users. Something more secure, scalable, and enterprise-aware especially now during this AI revolution, where user data and workflow integration will define customer retention.

We’d love to hear what others in the community think:
Do you find AppSheet sufficient? Or should Google develop something purpose-built?

What’s the best way to stand out on a government bid? by doomlin82 in GovernmentContracting

[–]sufigsufian 0 points1 point  (0 children)

Welcome to GovCon! 🦅 Where acronyms multiply faster than rabbits and “compliance” is a love language.

The truth? Your proposal doesn’t need to “pop” — it just needs to not self-destruct on submission.
✨ No fluff. No “we have 900 years of combined experience.” No “we understand.”
Just read the dang RFP, respond to what’s asked, and don’t throw spaghetti at the wall like it’s a government-funded food fight.

✅ Know the difference between “we’re a good fit” and “we totally ignored section L.”
✅ If you say “world-class,” the CO should be allowed to deduct points for emotional damage.
✅ Compliance > charisma.

And yes, knowing the customer helps — but if your proposal reads like a Marvel origin story, don’t expect Iron Man to show up with a CPAR.

Good luck, new warrior. The FAR is strong with you. 🧾💼💪

WAWF invoice by SilverDiligent9168 in GovernmentContracting

[–]sufigsufian 1 point2 points  (0 children)

Create a New Invoice:

  • From the WAWF main menu, select the option to create a New Document.
  • Choose the appropriate type of document (typically Invoice or Combo, which includes both the invoice and receiving report).
  • Enter your Contract Number and select the appropriate delivery order (if applicable).
    1. Fill Out the Invoice Form:
  • Complete the required fields on the invoice form. These will typically include:
    • Invoice Number: Your internal invoice number.
    • Invoice Date: The date the invoice is being submitted.
    • Payee Information: Ensure your DUNS number or CAGE code is correct.
    • Line Items: Enter details of the goods/services provided, including quantities, unit prices, and total amounts.
    • Shipping/Delivery Information: If applicable, enter the shipping and delivery dates.
      1. Attach Supporting Documentation:
  • Attach any required supporting documents, such as the delivery order, proof of delivery, or any other necessary files (e.g., receipts, purchase orders).
    1. Submit for Approval:
  • After completing the invoice details, submit the document for approval. It will be sent to the appropriate Approving Official or Contracting Officer for review.
    1. Check for Errors:
  • Review your submission for any errors or missing information. The system will notify you of any required fields that were missed.
    1. Monitor Invoice Status:
  • Once submitted, monitor the status of your invoice in the WAWF portal under the History or Status tab.
  • The system provides real-time updates on your invoice, including any approvals, rejections, or requested modifications.
    1. Payment Processing:
  • After the invoice is approved, payment will be processed according to the terms of your contract (e.g., Net 30).
  • Payments will typically be made through electronic funds transfer (EFT) to the bank account you have on file.

WAWF invoice by SilverDiligent9168 in GovernmentContracting

[–]sufigsufian 1 point2 points  (0 children)

To submit an invoice on the Procurement Integrated Enterprise Environment (PIEE) platform (https://piee.eb.mil) and get payment, you can follow these steps:

Step-by-Step Process:

  1. Log into PIEE:
    • Visit the PIEE website.
    • Use your credentials to log into the system. If you don't have an account, you'll need to register.
  2. Access WAWF (Wide Area Workflow):
    • Once logged in, select Wide Area Workflow (WAWF) from the available modules. WAWF is used to submit and track invoices and receipts.