KEMBAR78
Interview Prep | PDF | Invoice
0% found this document useful (0 votes)
7 views4 pages

Interview Prep

The document details the leadership experiences of a supervisor managing the DeCA/DHRA/DCAA teams during significant transitions, including a shift to telework and a new invoicing system. It highlights the supervisor's proactive approach to overcoming challenges, such as seeking guidance from colleagues and implementing effective strategies to clear unmatched disbursements. Additionally, it discusses contributions to audit readiness and the development of desk procedures to enhance operational efficiency within the team.

Uploaded by

Justin Matthew
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
7 views4 pages

Interview Prep

The document details the leadership experiences of a supervisor managing the DeCA/DHRA/DCAA teams during significant transitions, including a shift to telework and a new invoicing system. It highlights the supervisor's proactive approach to overcoming challenges, such as seeking guidance from colleagues and implementing effective strategies to clear unmatched disbursements. Additionally, it discusses contributions to audit readiness and the development of desk procedures to enhance operational efficiency within the team.

Uploaded by

Justin Matthew
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
You are on page 1/ 4

1.

what type of leadership role have you perfomred and where

-best detail is a supervisor example with orginizational benefit.

As a new supervisor for the DeCA/DHRA/DCAA teams i cmae in at a time of great change and challenges
especiallly for the DeCA team. last year i lead all 3 of my teams through the first fiscal year end in a
completly teleowrk enviroment and on that that have been leading my DeCA team through a chaotic
transiton from DBS (Defense Buisness manamgment systems) to the new system that most of ther rest
of AP maintenaces uses to proceess agency invoices (Dai). The challenges that I faced during the
transition is that I was completely unfamiliar wit hthe teams work, and wer wer under pressured to get
as many Unmateched Disbursmets cleared cleared for FYE. (Unmatched Disbursment being a payment
that has to be matched to the proper PO before it can be released and paid.) My team was preasured to
get as many UMD's clread for FYE becasue of the conversion. (My team is normally revolving year funds
so this normally doesnt matter). To overcome thzse challenges i had to admit that i was out of my depth.
So i asked my lead Linda to show me how they did their basic processing of UMDS', that wasy i could
speak more comfortabley and more authoritatevly on the teams work with UM. As FYE went on the
pressure was still on to clear as many UMD's as possible, so me and Linda came up with a plan to target
what we thought would be the best way to deal with the UMDS. We found out that most UMD's under
$2500 could be easily be researched, and our team had been given permission to Post these to a newly
established PO. So with that we went and gather all the UMD's out in DRRT filtered them down to
anytthing below $2500, and broke those across 7 team member. Through hard work and credit time my
team was able to complete this project over a week ahead of schedule leaving the remainder of
September for the FYE workload. In that project we were able to clear 900 UMDS, and by the end of FYE
we wre able to clear roughly 3000, and reduce the amount to be transfered to DAI by half.

2. There will be times where problems arise where proper point of contact is not possible, what would
you do in these times. .

THe first thign i would do is read and look a the relevant regulations as to what actions i should take,
when I am dealing with whatever issue. From their i would look at what my SOP/(Standard Operating
Procedures) would have to say on any given issue. Fail Failing that i would look at closed Darts ticekts to
see if their had been any isntances of how this issue was dealt with. From their if I still had not found
anything I would reach out to my cowoerkds and ask them if they had to deal with an issue like this.
Failing this, this would be the time I would elevate this to a lead/supervisor.

3.

1. Mocas. As an accounting technician for BAM Erroenosu pay team i worked useing the program
MOCAS. (mechanization of contract administrative services. In using programs like MOCAS it wa my job
to check to see if invoices were adhereing to FARS and dfars regulations. First i would check the WAWF
invoices against what was in the BUISNESS ACTIVING MONITORING (BAM) workbetch to see that htey
matched. FROM their i would long into MOCAS YCU@ (New Contracts Mod corrections 5(System
inquires) then 12( absratct inquires) from their I would select the invididual records and look at the Clin
and ACRN to as wellas match this with the invoice and see that were were not overbilling, if evertying
looked fine, i would approve this invoice in Bam & allow it to be paid. If i was wrong i would navigate to
the invoicd date entry menu in Mocas through YCPM, and would create a batch using the Julian calendar
date, and issue a recode on the invioce , and issue a recode on the infoice if i found it was in errorm,
most of the time this was a recode E11f Duplciate payemnt. Other systems that I aslo occasionaly
worked with wor IAPS/TQ and ebs when i helped out other members in the EBS team

In my time as a technician for recoon I also uded mocas but for a deeper level of work. I would mocas
and other pgorgrams to fix deep rooted contract problems. For example i would often recieve this
invoice is over billng and can't figure out why. I would first verify the current invoice agains clins and
acrns in Mocas, I would checkto see what Mocas said the current obligation was and current
disbursment levels on said clin and acrns. IF it was over billed on the AACRN i would go and check
agaisnt SDW (share Data Warehosue /Scaph) to get a rough idea of what disbursment was liek across the
entire contract. Often i would see that it was that mod was not successfly added into mocas that would
be the cause of this, but was present elsewhere in EDM electronic document management or EDA
Electronic document access. I would email contract input and instruct them to add it in this case. IF could
not find the issue iwould do a full audit using either SCRT or Excel and go throuhg every mod establishing
money to acrns and clins and create a record and then go back through disbursmetns and see what they
overbilled. From their I would go back and check the invoices and see what they billed and when i found
the issue i would issue a 1081 through the standard contract reconcilliation tool (SCRT) and check back
in mocas the following day along with other programs to make sure sure that my correction had gone
thorugh. From their i would write up my audit summary and send that to my lead so that my invoice
could be released to to pay. In cases where the customer or soemone else in Dfas had made a mistake i
would tell entilement to recode to JAREQ so that they could see what was going on.

4. What is the most signficant contribution you have made to an Audit/ audit readiness

The most signficant contribution that I made to an audit was an independent audit that I started. The
case was skikorsky after they had recently been sold to Lockheed. The issue was they had about 30 acrns
acros about 10 different clins that were being over billed and udner billed, that really was not making
much sense. So i did the full audit using SCRT, and manually input to each and every obligation in and
every disbursment. The contractor was doing alot of credits and debits whenever it hit its obligation limit
so this definietly contributed. However, what i discovered by reading the PGi clauses of the contract is
that DFAS was still paying this as if were paying in Sequential ACRN order which i found out tha back in
MOD 2 it was changed to PGI 12 other pay as billed. So a great chunk of the error had been on DFAS's
end. I escalated this up to my lead and supervisor then to an analyst. I worked with my analsyt to
painstakenling go through every invoice that was added in scrt in the full audit section and match it to
waht the obligations and clins were suposed to be and ran it. In the end their was well over 550
adjusments to fix this moving over several millino dollars aroud this contract. In the end were able to get
this balanced so that the contract would be able to pay without any more issues.
An example of the best way I as a tech contributed to Audit readiness was, when ever an adjustment
need to be done in mocas is that first i would offer back up and justifcation for any change i would do. I
would do this by putting together an Adjustment package, If i had to move 1000 dollars from clin 0001
ACRN AA to Clin 0002 AB i would provide them following, Copy of the current invoice and voucher #.
Current Snapshot of the amount availaibe on the Clin/ACRN, and a copy of any relevant modifications to
the contract that might justfify the moving of funds. I would get the copy of the invoice by going into
WaWF (wide area workflow) inputing the contract # and shipment number and bring thatt invoice and
printing it to PDF, then i would go into mocas yinv 5-12 and pull up the contract number and input the
select individaul records and pull up the clin and acrn and take screen shots of both, when I needed to
provide a copy of the modification, I would log into EDA input hte contract # and pull up the contract and
search out the relevant mod and print to PDF. to pull the VOucher i would go into EDM (Electronic
Document Managment) input the contract and pull up the voucher. With that I would write up an audit
summary noting what I had found and give my reasoning for providing an adjustment move. Example
mod 1A obligated 1000 dollars to clin 0002AB but was mistakenly added to 0001 AA, I would then fix
this by doing an obligation adjustment and any necessary disbursment level adjustments, and send this
package to my lead for processsing. Once this had done processing i would submit this pacakge in EDM
attaching to the EDM case so that my whole work could be seen and recounted easily by an auditor. This
was the way i as a tech contrimbuted most to Audit readiness.

Me and my team provide audit requestied time- sensitive payment samples for DeCA/DHRA/DCAA. My
team has also worked to prove process breifing to the auditors so that they can approve our work
processes

5. Please describe a project you lead and what wer the results.

Currently I am coming nearing the end of Desk Prodcedure project for my DHRA/DCAA teams. Coming
into my team which has gone throug several supervisors in quick succession I realized they hand't had
any of their processes written down in anywhere. So i took inspiration from a project that I worked back
under the BAM erroneous pay team, which was a desk procedure project and decided to have my lead
and technicians make one, with the side benefit of this being in DAI this would be able to help my DeCA
team work their invoices since they just converted to this system. I first drew up a plan of what I wanted
this guide to have. I wanted it to have every procedure that they worked on in DAI, and any auxilary
systems they used. I wanted it to be decently detailed but not necessarily to SOP standards. I then took
this project Idea to my boss and we had a discussion going back and fort wher she defintely pushed a
more in depth guide. I realized that this would potentially push the end date farther out than i would of
oginally liked, I wanted it done by this month/early January. We eventually came to the agreement that
this will still be a desk procude but wit the goal of expanding it later on if neccessary so that it could be
converted into an SOP. Wit this i went a head and set meetings with my techs and Laid out what i
wanted. I provided them with a copy of the OLD SOP that i had work on under BAM AP maintenace and
told them what my end goal was. I told them taht each section their would be 1 table of contents and 2
sections. Table of contets would list what procedue and where to find it. the sections would be broken
down between lead and technician. Each process having a descriptive paragraph of what this process
was and why it needed to be done. Through weekly back and forth meetings i was their guide and
answered questions they might of had, like how long should it be. My answer being a s long as necessary
but we don't want to over burden people we want this to be pretty easily to be understandable by a
person who is just coming into this postion. Currently I am awaiting the final draft of this project and
once it is done I will have my DeCA techs test it to see if it works, and then it will be completed and be
maid available to anyone who comes into the DHRA/DCAA postion and be usefull in being the starting
point for the DeCA guide that i plan on starting.

talk about my DeCA excell DSSN small project, and talk about old SOP project

6. You are part of a 4 person team and are doing 50% of the work, do you take this to your boss.

IT depens if this is not affecting my work and my boss feels that I am capable of I welcome the challege. I
would talk to them about becoming the offical head of this project at that point, and sent up one on one
meetings for continued guidance in how i should go forward. however if the project did require more of
my work I would still tak to my boss about becoming the lead of the project, I would discuss that i am
not capable of doing this without sacrificing my other work. So in that case i would like the ability to
assign people the work that they would need to do so that this is more equatibally distributed. I would
also go and ask people what it was they specifically wanted to take up. in my bam erroneus pay team I
was the point of contact for MOCAS. I work with my other techs Robin and Schriner to divide up the
work. I took control of Highdollar risk managment cases, robin took preval and Ramel took mongoodses
toghther over teh course of a month we would meet and check up on eachothers work trying to catch
bits of informatin that maybe we had mist. and the the end we were able to get this desk procedure
submitted and approved by upper managment for offical use in guideign future techs.

You might also like